[Bug libstdc++/41645] Massive failures in parallel test mode

2010-01-28 Thread paolo dot carlini at oracle dot com
--- Comment #15 from paolo dot carlini at oracle dot com 2010-01-28 16:27 --- In the meanwhile I have been able to build and run make check-parallel on a x86_64-apple-darwin10.2.0, and indeed the specific problem seems fixed. Beyond that, I'm pretty sure a judicious use of DYLD_LIBRARY

[Bug libstdc++/41645] Massive failures in parallel test mode

2010-01-28 Thread paolo dot carlini at oracle dot com
--- Comment #14 from paolo dot carlini at oracle dot com 2010-01-28 15:23 --- If I understand correctly at least part of this issue, now the situation should be somewhat better, because a few days after the original conversation in the audit trail, I enabled extern templates for paralle

[Bug libstdc++/41645] Massive failures in parallel test mode

2009-10-09 Thread joseph at codesourcery dot com
--- Comment #13 from joseph at codesourcery dot com 2009-10-09 19:42 --- Subject: Re: Massive failures in parallel test mode On Fri, 9 Oct 2009, chris at bubblescope dot net wrote: > LD_LIBRARY_PATH doesn't exist on Mac. Usually linking libraries together 'just It's called DYLD_LIBR

[Bug libstdc++/41645] Massive failures in parallel test mode

2009-10-09 Thread chris at bubblescope dot net
--- Comment #12 from chris at bubblescope dot net 2009-10-09 17:51 --- LD_LIBRARY_PATH doesn't exist on Mac. Usually linking libraries together 'just works', but in this case it seems to have broken. By configuring with --enable-fully-dynamic-string, I get a working compiler (actually b

[Bug libstdc++/41645] Massive failures in parallel test mode

2009-10-09 Thread paolo dot carlini at oracle dot com
--- Comment #11 from paolo dot carlini at oracle dot com 2009-10-09 15:31 --- (In reply to comment #10) > To sum up the current state, as things are getting confusing: A bit yes ;) > Compiling 'testsuite/21_strings/basic_string/inserters_extractors/char/1.cc -I > testsuite/util -O2' >

[Bug libstdc++/41645] Massive failures in parallel test mode

2009-10-09 Thread chris at bubblescope dot net
--- Comment #10 from chris at bubblescope dot net 2009-10-09 15:10 --- To sum up the current state, as things are getting confusing: Compiling 'testsuite/21_strings/basic_string/inserters_extractors/char/1.cc -I testsuite/util -O2' using /newgccsvn/bin/g++ (recent svn compile) or /usr/

[Bug libstdc++/41645] Massive failures in parallel test mode

2009-10-09 Thread paolo dot carlini at oracle dot com
--- Comment #9 from paolo dot carlini at oracle dot com 2009-10-09 14:51 --- Sorry, your 'however' confused me. So, you *are* linking versus the new library, right? In that case it is *incorrect* to pass -D_GLIBCXX_FULLY_DYNAMIC_STRING in the command line, since your new library has not

[Bug libstdc++/41645] Massive failures in parallel test mode

2009-10-09 Thread paolo dot carlini at oracle dot com
--- Comment #8 from paolo dot carlini at oracle dot com 2009-10-09 14:46 --- So, the problem is exactly that you *are* using the system libraries, a mix of the new headers and the system library. This is in general unsupported of course. While apparently we *do* have a problem in tests

[Bug libstdc++/41645] Massive failures in parallel test mode

2009-10-09 Thread chris at bubblescope dot net
--- Comment #7 from chris at bubblescope dot net 2009-10-09 14:20 --- Further: If I add -D_GLIBCXX_FULLY_DYNAMIC_STRING, the code compiles fine! However, if I run otool on my executable, it says it is linked with: Load command 10 cmd LC_LOAD_DYLIB cmdsize 64 na

[Bug libstdc++/41645] Massive failures in parallel test mode

2009-10-09 Thread chris at bubblescope dot net
--- Comment #6 from chris at bubblescope dot net 2009-10-09 14:16 --- Ah yes, something I should have tried earlier. The resulting compiler generally works fine, until I add -D_GLIBCXX_PARALLEL, when things break. I only seem to get a problem when I have enough optimisation to inline f

[Bug libstdc++/41645] Massive failures in parallel test mode

2009-10-09 Thread paolo dot carlini at oracle dot com
--- Comment #5 from paolo dot carlini at oracle dot com 2009-10-09 13:52 --- Indeed, the system library should not be used at all, but in your example above the system library *is* used unless you make sure to properly install everything, set the appropriate LD_LIBRARY_PATH, etc. In oth

[Bug libstdc++/41645] Massive failures in parallel test mode

2009-10-09 Thread chris at bubblescope dot net
--- Comment #4 from chris at bubblescope dot net 2009-10-09 13:21 --- I have confirmed that after compiling with 'make check-parallel', the code: #include int main(void) { string s; s = "X"; } Fails when compiled with: /gccsvn/bin/g++ test.cc libtestc++.a -fopenmp Fails with the s

[Bug libstdc++/41645] Massive failures in parallel test mode

2009-10-09 Thread paolo dot carlini at oracle dot com
--- Comment #3 from paolo dot carlini at oracle dot com 2009-10-09 12:59 --- ... for sure the libtestc++.a thing is *very* mysterious... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41645

[Bug libstdc++/41645] Massive failures in parallel test mode

2009-10-09 Thread chris at bubblescope dot net
--- Comment #2 from chris at bubblescope dot net 2009-10-09 12:57 --- I shall try to track it down -- it wouldn't suprise me if this is a snow leopard bug, as there has been a few issues with the default system compiler switching from 32-bit to 64-bit. -- chris at bubblescope dot net

[Bug libstdc++/41645] Massive failures in parallel test mode

2009-10-09 Thread paolo dot carlini at oracle dot com
--- Comment #1 from paolo dot carlini at oracle dot com 2009-10-09 12:51 --- Can you sat when did this problem start? Because I'm running again the tests on x86_64-linux and everything seems in good shape so far (in 23_containers now), thus I can't confirm it, the problem seems definite