This is the mail archive of the mailing list for the libstdc++ 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: Rewriting bitmap_allocator

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/ (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.


You can find the details of the failures in
$target/libstdc++-v3/testsuite/libstdc++.log under the build

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

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