This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [MinGW] Allow Building GCC with --disable-sjlj-exceptions


References: <http://gcc.gnu.org/ml/gcc-patches/2006-06/msg00786.html>
            <http://gcc.gnu.org/ml/gcc-patches/2006-06/msg00790.html> 

Hello Ranjit, Brian

Brian Dessent wrote:
> Ranjit Mathew wrote:
> 
>> -#define DWARF2_UNWIND_INFO 0
>> +#define DWARF2_UNWIND_INFO 1
> 
> This makes no sense at all.  DW2 EH is seriously broken under
> cygwin/mingw, and it's not clear that this is even fundamentally
fixable
> (e.g. the situation of throwing an exception in a callback from third
> party code that doesn't use DW2 like the win32 API.)  Someone posted
on
> the mingw list recently with a testcase showing even further breakage
in
> DW2 EH when throwing across a DLL boundary.  Flipping this switch
should
> be the *last* step that happens after all these other problems are
> fixed, not the first step.  SJLJ is still the only sane default for
> cygwin/mingw.


I would disagree about the "seriously broken". I have been using it in
my own gcc toolset on mingw for three years and I am convinced that it
has more benefits than deficiencies. 

The report of "even further breakage" was actually exciting to me
because the reporter cared enough to also submit a tidy little testcase
Now we can fix the bug. (FWIW, a very similar initialization bug was
reported on the mingw list when the experimental EH-acoss-DLL-boundaries
-- using SjLj -- was first unleashed on mingw users for testing.)


I agree with Ranjit that the option to enable DW2 EH should be made
available on mingw32 target.

But I think it should wait until stage 1.

Danny

   


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]