http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54407
--- Comment #7 from Jack Howarth <howarth at nitro dot med.uc.edu> 2012-10-14
20:14:01 UTC ---
(In reply to comment #6)
> > The patch in comment 4 with...
> >
> > make -k check
> > RUNTESTFLAGS="conformance.exp=30_threads/condition_variable/54185.cc
> > --target_board=unix'{-m32,-m64}'"
> >
> > produces...
>
> Could you check in the log file that the test is actually run?
The dg-compile line oddly seems to suppress the running of the compiled test.
Dropping that line gives...
Native configuration is x86_64-apple-darwin11.4.2
=== libstdc++ tests ===
Schedule of variations:
unix/-m32
unix/-m64
Running target unix/-m32
Using /sw/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /sw/share/dejagnu/config/unix.exp as generic interface file for target.
Using
/sw/src/fink.build/gcc48-4.8.0-1000/gcc-4.8-20121007/libstdc++-v3/testsuite/config/default.exp
as tool-and-target-specific interface file.
Running
/sw/src/fink.build/gcc48-4.8.0-1000/gcc-4.8-20121007/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp
...
=== libstdc++ Summary for unix/-m32 ===
# of expected passes 2
Running target unix/-m64
Using /sw/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /sw/share/dejagnu/config/unix.exp as generic interface file for target.
Using
/sw/src/fink.build/gcc48-4.8.0-1000/gcc-4.8-20121007/libstdc++-v3/testsuite/config/default.exp
as tool-and-target-specific interface file.
Running
/sw/src/fink.build/gcc48-4.8.0-1000/gcc-4.8-20121007/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp
...
=== libstdc++ Summary for unix/-m64 ===
# of expected passes 2
=== libstdc++ Summary ===
# of expected passes 4
Why you want to bother to compile the test are darwins which can't safely run
it anyway. That seems rather pointless.
