Dwarf2 exception handling on Win32
Hi all,
For those people who arrived to the party too recently to remember, it was always Mingw's intention to shift to Dwarf2 EH. It was just slow in coming. One of the reasons it took so long was that for a long time, Mingw's compiler was not considered to be a first-class target, but was only a set of patches maintained by Mingw.org itself. Now Mingw -is- a first-class GCC target, and their compiler patches do make it into GCC trunk somewhat faster.
Now that DW2 is becoming the default on Win32, shifting back to old SJLJ would be going -against- progress. (And be bad timing, too :-)
Anyway, DW2 is what I will be using from now on.
bob
2010/2/3 Bob Jamison <ishmalius@...400...>:
Now that DW2 is becoming the default on Win32, shifting back to old SJLJ would be going -against- progress. (And be bad timing, too :-)
"Becoming"? Is it the default in GCC 4.4.1 or not?
What exactly is the rationale for using Dwarf2 EH right now? That it will work correctly in the future?
For me the more important considerations were that it might cause Windows-specific crashes and will bloat the code. (Dwarf2 gtkmm is 15MB while SJLJ gtkmm is less than 4MB.) I just don't see a compelling reason to use it at the moment. The situation might change once we move to building with GCC 4.5.
Regards, Krzysztof
-----Original Message----- From: Bob Jamison [mailto:ishmalius@...400...] Sent: Wednesday, February 03, 2010 13:21 To: inkscape Subject: [Inkscape-devel] Dwarf2 exception handling on Win32
[...] Now that DW2 is becoming the default on Win32, shifting back to old SJLJ would be going -against- progress. (And be bad timing, too :-)
I think everybody is in favor of progress :-) But what exactly is the progress (relevant for Inkscape) that compensates for introducing crashes?
Did someone try to use DW2 and "--shared-libgcc" for building the devlibs to see if that fixes the crashes?
-Johan
participants (3)
-
unknown＠example.com -
Bob Jamison -
Krzysztof Kosiński