This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: Rewriting bitmap_allocator
- From: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- To: Dhruv Matani <dhruvbird at gmail dot com>
- Cc: Benjamin Kosnik <bkoz at redhat dot com>, "libstdc++" <libstdc++ at gcc dot gnu dot org>
- Date: Mon, 29 Apr 2013 09:18:27 +0100
- Subject: Re: Rewriting bitmap_allocator
- References: <CAOG+gn2uvg-tfhj8rbo9dP1TY_iOTKXN7fyYdLj_YiR=2HWzDg at mail dot gmail dot com> <20120625154511 dot 2da206f7 at adair> <CAOG+gn1JJD7N3WssVeuQ2vavwB1P6UOmRop6TB3BuYebjbgU-A at mail dot gmail dot com> <20120626132507 dot 23889470 at adair> <CAH6eHdSL7WpRsQme0qEOZ3V64DU4Fbcgrr743O2MN4FrQkTfKA at mail dot gmail dot com> <CAOG+gn26EUbgrXdHkuGPBRF=nUtQ3_4WiXFK7SYGfPj2ofVoKw at mail dot gmail dot com> <CAH6eHdS1wSU=S1M8TYHwrj_YL9OV8dqd-dAxX=jHWOXTpmE2iw at mail dot gmail dot com> <CAOG+gn2+KAv7MFxYbDAhsEwMsqrFx_doPsQTUEB6mKNEKv3EFQ at mail dot gmail dot com> <CAOG+gn3O6+3iLb7bDyDCFdXb7=JG6q13=ToUiJBD=_axvquGCQ at mail dot gmail dot com>
On 29 April 2013 01:35, Dhruv Matani wrote:
> Hello,
>
> So I've been able to get bitmap_allocator to compile with the build process
> on the latest (on svn: rev 198365) gcc.
>
> However, I have some test failures in "make check-target-libstdc++-v3".
>
> Running target unix
> Using /usr/share/dejagnu/baseboards/unix.exp as board description file for
> target.
> Using /usr/share/dejagnu/config/unix.exp as generic interface file for
> target.
> Using
> /home/dhruvbird/projects/gcc-devel/libstdc++-v3/testsuite/config/default.exp
> as tool-and-target-specific interface file.
> Running
> /home/dhruvbird/projects/gcc-devel/libstdc++-v3/testsuite/libstdc++-abi/abi.exp
> ...
> FAIL: libstdc++-abi/abi_check
> Running
> /home/dhruvbird/projects/gcc-devel/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp
> ...
> FAIL: 17_intro/headers/c++200x/all_pedantic_errors.cc (test for excess
> errors)
> ^Cgot a INT signal, interrupted by user
>
> === libstdc++ Summary ===
>
> # of expected passes 2234
> # of unexpected failures 2
> # of expected failures 6
> # of unsupported tests 285
>
> Any idea what I'm missing here, and how to fix it. I can send a diff if that
> helps.
Hi,
You can find the details of the failures in
$target/libstdc++-v3/testsuite/libstdc++.log under the build
directory.
Instead of waiting for the entire testsuite to run you can run
selected tests in the $target/libstdc++-v3 dir with e.g.
make check RUNTESTFLAGS=conformance.exp=17_intro/headers/c++200x/*
or to run just the ABI check:
make check-abi
The ABI check is probably failing because you've added some symbols to
the library, which need to be exported with the correct symbol
version.