> I can confirm that gnat gcc 4.1.1 does *not* correctly handle SJLJ
> exceptions, at least on MinGW where SJLJ is currently the only viable EH
> mechanism.
The 2 SJLJ mechanisms should be available there, so you could try to use
GCC SJLJ instead of GNAT SJLJ (set ZCX_By_Default to True in system
> Eric Botcazou writes:
> > You need GCC 3.x or GCC 4.2 for GNAT SJLJ exceptions to work.
>
> Do you mean that it does not work with GCC 4.1.1? That would be very
> bad news.
I can confirm that gnat gcc 4.1.1 does *not* correctly handle SJLJ exceptions,
at least on MinGW where SJLJ is currently
> Do you mean that it does not work with GCC 4.1.1?
Yes, it doesn't work in the 4.1.x series.
> > [2] describes GCC SJLJ, which is not the same as GNAT SJLJ.
>
> How different?
The latter is a "primitive" form of SJLJ, the former is more structured.
> I was somehow suspecting that gnat1 support
Eric Botcazou writes:
> You need GCC 3.x or GCC 4.2 for GNAT SJLJ exceptions to work.
Do you mean that it does not work with GCC 4.1.1? That would be very
bad news.
>> From [2] it looks like this is a configure-time option only.
>
> [2] describes GCC SJLJ, which is not the same as GNAT SJLJ.
How
> I'd like to know how I should go about building GCC such that I can choose
> between SJLJ and ZCX at compile time, using --rts=sjlj.
$srcdir/configure --enable-languages=ada --disable-libada
make [bootstrap]
make -C gcc gnatlib-sjlj
make install
in the $prefix/lib/gcc/$target/$version directory:
Hi, after reading [1] and [2] I'm a bit confused. I'd like to know how
I should go about building GCC such that I can choose between SJLJ and
ZCX at compile time, using --rts=sjlj. From [2] it looks like this is a
configure-time option only. Is it necessary to configure gcc twice and
produce two