MinGW gcc 3.x, 4.x and exceptions

1 msg	Wide Streams
4 msg	MINGW I/O support for file sizes > 2GB (LFS ...
2 msg	#define WINVER 0x0400
11 msg	Why does g++ not link with libstdc++?
3 msg	how to compile and link a library
1 msg	Hey Guys
5 msg	Compile error using mingw
2 msg	'include/c++/ext' missing fromgcc-part-c++-4.3....
1 msg	FMTID_SummaryInformation andFMTID_UserDefinedPr...
2 msg	how to realize mouse programming
3 msg	looking for tiny light cross platform filesyste...
2 msg	MinGW GCC Development Plan
3 msg	how to use the read/write
74 msg	GCC 4.3.0 20080502 (alpha) Released - Please he...

MinGW gcc 3.x, 4.x and exceptions
\ alvaro (3 May 2008)
. \ Brian Dessent (3 May 2008)
. . \ alvaro (3 May 2008)
. . \ John E. / TDM (4 May 2008)
. . . \ Charles Wilson (4 May 2008)
. . . \ Lothar May (9 May 2008)
. . . . \ David Daeschler (9 May 2008)
. . . . . \ Danny Smith (11 May 2008)
. \ Brian Dessent (3 May 2008)
. \ Aaron W. LaFramboise (5 May 2008)

4 msg	dllwrap 2.17.50 20060824
12 msg	strtod is not C99-compatible
4 msg	Test program crashes with g++ 4.2.1-dw2 usingli...
25 msg	imlib2
3 msg	Disassembly of stack frame

Subject:	MinGW gcc 3.x, 4.x and exceptions
Group:	Mingw-users
From:	alvaro
Date:	3 May 2008

First, thanks Charles Wilson for your explanation of the development and
patching of MinGW (it seems even more effort than I thought), and of
the SJLJ/DW2 exception issues.

For a long time I have been reluctant to use exceptions in my programs
due to problems such as implementation bugs (many years ago),
incompatibility between compiler versions, code size increase, etc. even
if I think it is the way to handle errors.

More recently I was about to go ahead and write exception aware code,
but then I read about problems throwing exceptions across DLL
boundaries, the different models (SJLJ vs DW2), and the need of a shared
libgcc.

I tested gcc 3.4.5 and found no problem: an exception thrown by a DLL
(loaded on demand with LoadLibrary) was caught by the main exe. Not sure
if problems are only in DLLs linked with import libs.

Now, in gcc 4.x, they say in order to throw exceptions across DLLs you
must link a shared libgcc. IMHO this kind of breaks the MinGW philosophy
of not depending on additional DLLs (see the home page), possibly the
main difference with cygwin and one of the reasons I prefer MinGW.

I would say it is *very* important to keep MinGW this way and still
support exceptions. If that implies using the "old" SJLJ system, I
wouldn't mind. I can admit a little performance loss. If 3.x can do it,
why can't 4.x?

(Charles already mentioned that some developers would get annoyed by
this shared thing and I wanted to emphasize it with my opinion)

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
MinGW-users mailing list
MinGW-users

You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users