libstdc++, -m64 and can't find atom for N_GSYM stabs

[Andreas Jaeger]

Eric Christopher <echristo@apple.com> writes:

>> Once the noise from those linker warnings is removed from the libstdc++-v3 testsuite
>> results at -m64 on Darwin PPC, we find that the failures drop from 54 to just 6. So
>> we actually only have four additional libstdc++-v3 testsuite failures at -m64
>> compared to -m32. These are...
>>
>> FAIL: 21_strings/basic_string/cons/char/1.cc execution test
>> FAIL: 21_strings/basic_string/cons/wchar_t/1.cc execution test
>> FAIL: 21_strings/basic_string/insert/char/1.cc execution test
>> FAIL: 21_strings/basic_string/insert/wchar_t/1.cc execution test
>>
>> which certainly would appear as if they are all related bugs. Can you try
>> the above check on x86_64 and see how many regressions you have when the
>> linker warnings suppressed?
>
> For i386 vs x86_64 I'm getting a different set of pass/fail between
> the two. I do, however, have those 4 failures on x86_64 and not on
> i386.

Those come AFAIR from a wrong locale path.  I'm not sure whether a bug
is filed for this or whether it was only discussed at some mailing
list,

Andreas
-- 
 Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/
  SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: not available
URL: <https://gcc.gnu.org/pipermail/gcc/attachments/20060902/d7e99b8e/attachment.sig>