Eric Christopher <[EMAIL PROTECTED]> 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 failur
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/
Eric,
I just reran "make -k check RUNTESTFLAGS='--target_board "unix{-m64}"'" in
the
darwin_objdir/powerpc-apple-darwin8/libstdc++-v3 directory after applying the
following patch to suppress the "can't find atom for N_GSYM stabs" ld64 linker
warnings...
--- gcc-4.2-20060825/libstdc++-v3/test
Eric,
So far the smallest test case I can come up with reproduces the
"can't find atom for N_GSYM stabs" ld64 linker warning in Darwin is...
#include
#include
// uneq_allocator as a non-empty allocator.
void
test01()
{
bool test __attribute__((unused)) = true;
using namespace std;
typ
Jack Howarth wrote:
Geoff,
It appears that this issue with the ld64 link issuing warnings of
"can't find atom for N_GSYM stabs" is not specific to gfortran. I finally
figured out the correct syntax to run a complete make check so that the
libraries as well as gcc are checked. FYI, the trick is
Geoff,
It appears that this issue with the ld64 link issuing warnings of
"can't find atom for N_GSYM stabs" is not specific to gfortran. I finally
figured out the correct syntax to run a complete make check so that the
libraries as well as gcc are checked. FYI, the trick is to use the
equal sign
