[uClibc] Re: exception test
Peter S. Mazinger
ps.m at gmx.net
Sun Jun 5 03:03:17 MDT 2005
On Sat, 4 Jun 2005, Peter S. Mazinger wrote:
> On Sat, 4 Jun 2005, Peter S. Mazinger wrote:
>
> > On Fri, 3 Jun 2005, Manuel Novoa III wrote:
> >
> > Sending to list now
> >
> > > Hi Peter,
> > >
> > > This is something we use as a quick check.
> >
> > throw2.cpp aborts after '1 Throwing out_of_range()' on all gcc's I have
> > built w/o --enable-sjlj-exceptions (3.4.3/3.4.4/4.0.0).
> > The test done w/ 3.3.6 built w/ sjlj exceptions is going further (failing
> > only at float, that is probably normal)
> >
> > I have currently no gcc>=3.4 built w/ sjlj exceptions.
> >
> > I think sjlj exceptions will come back into buildroot for all versions
> > (not only for <=3.3.3)
> >
> > uClibc++ sources have also an excepttest.cpp file that can be taken for
> > testing (it fails in all configs where throw2 fails too and is ok w/
> > gcc-3.3.6+sjlj-exceptions)
>
> I have rebuilt gcc-3.4.4 w/ sjlj-exceptions, both the uclibc++ test and
> and throw2 perform ok against libstdc++ and uclibc++, so up to 3.4.4 (but
> probably 4.0.0 too) need --enable-sjlj-exceptions
>
> The tests were done in gentoo uclibc native environment.
Forgotten to mention, ARCH=x86 and the gentoo builds differ from
buildroot. Gentoo uses --disable-libunwind-exceptions, buildroot does not
use that.
Peter
--
Peter S. Mazinger <ps dot m at gmx dot net> ID: 0xA5F059F2
Key fingerprint = 92A4 31E1 56BC 3D5A 2D08 BB6E C389 975E A5F0 59F2
More information about the uClibc
mailing list