Re: [patch] Clean up detection of SJLJ exceptions in target libraries

2015-05-15 Thread Ian Lance Taylor
On Wed, May 13, 2015 at 10:52 AM, Eric Botcazou wrote: >> The libgo parts are fine, but since libgo is mirrored from an external >> repository I'll commit those parts myself. > > Thanks! > >> I assume I can go ahead and commit them now? > > Yes, you can, the libgo bits are independent. libgo port

Re: [patch] Clean up detection of SJLJ exceptions in target libraries

2015-05-13 Thread Eric Botcazou
> The libgo parts are fine, but since libgo is mirrored from an external > repository I'll commit those parts myself. Thanks! > I assume I can go ahead and commit them now? Yes, you can, the libgo bits are independent. -- Eric Botcazou

Re: [patch] Clean up detection of SJLJ exceptions in target libraries

2015-05-13 Thread Ian Lance Taylor
On Tue, May 12, 2015 at 9:42 AM, Eric Botcazou wrote: > > 6 target libraries in the tree detect whether they are being compiled by a > compiler configured for setjmp/longjmp exceptions: libada, libgcc, libgo, > libjava, libobjc and libstdc++. They can be divided into 3 categories: > 1) libada on

Re: [patch] Clean up detection of SJLJ exceptions in target libraries

2015-05-13 Thread Eric Botcazou
> This patch fixes an issue preventing mingw-w64 i686 dwarf2-eh > bootstrapping described at: > > http://sourceforge.net/p/mingw-w64/mailman/message/34101954/ > > I'm assuming this has more to do with switching away from the current > sjlj configuration method since configuring gcc with > "--disa

Re: [patch] Clean up detection of SJLJ exceptions in target libraries

2015-05-13 Thread Matt Breedlove
This patch fixes an issue preventing mingw-w64 i686 dwarf2-eh bootstrapping described at: http://sourceforge.net/p/mingw-w64/mailman/message/34101954/ I'm assuming this has more to do with switching away from the current sjlj configuration method since configuring gcc with "--disable-sjlj-excepti

Re: [patch] Clean up detection of SJLJ exceptions in target libraries

2015-05-13 Thread Jonathan Wakely
On 12/05/15 18:42 +0200, Eric Botcazou wrote: libstdc++-v3/ * acinclude.m4 (GLIBCXX_ENABLE_SJLJ_EXCEPTIONS): Delete. * configure.ac: Remove GLIBCXX_ENABLE_SJLJ_EXCEPTIONS. * config.h.in: Regenerate. * configure: Likewise. * libsupc++/eh_personality.cc: Repl

Re: [patch] Clean up detection of SJLJ exceptions in target libraries

2015-05-13 Thread Andrew Pinski
On Tue, May 12, 2015 at 9:42 AM, Eric Botcazou wrote: > Hi, > > 6 target libraries in the tree detect whether they are being compiled by a > compiler configured for setjmp/longjmp exceptions: libada, libgcc, libgo, > libjava, libobjc and libstdc++. They can be divided into 3 categories: > 1) lib

Re: [patch] Clean up detection of SJLJ exceptions in target libraries

2015-05-13 Thread Eric Botcazou
> Generally OK. However, please confirm with ian on the libgo bits just > in case you're hitting something that's shared with golang. OK, I can certainly wait for Ian's approval for the libgo bits. > We could certainly consider cleaning up the targets (hppa). That'd be a > fine follow-up :-) I

Re: [patch] Clean up detection of SJLJ exceptions in target libraries

2015-05-12 Thread Jeff Law
On 05/12/2015 10:42 AM, Eric Botcazou wrote: Hi, 6 target libraries in the tree detect whether they are being compiled by a compiler configured for setjmp/longjmp exceptions: libada, libgcc, libgo, libjava, libobjc and libstdc++. They can be divided into 3 categories: 1) libada only checks th

[patch] Clean up detection of SJLJ exceptions in target libraries

2015-05-12 Thread Eric Botcazou
Hi, 6 target libraries in the tree detect whether they are being compiled by a compiler configured for setjmp/longjmp exceptions: libada, libgcc, libgo, libjava, libobjc and libstdc++. They can be divided into 3 categories: 1) libada only checks the preprocessor macro __USING_SJLJ_EXCEPTIONS__