This is the mail archive of the mailing list for the GCC 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: regress and -m64

   Why don't you try a normal multi-lib build without any
extra flags. At the moment, considering how much noise is on
the testsuite results on Darwin due to this linker warnings, I
don't think its really helpful to bother exploring corner cases
of building gcc trunk with unique flags. Make sure you have...

--- gcc-4.2-20060825/libstdc++-v3/testsuite/lib/   2006-08-26 11:22:52.000000000 -0400
+++ gcc-4.2-20060825/libstdc++-v3/testsuite/lib/prune.exp       2006-08-26 11:23:39.000000000 -0400
@@ -29,5 +29,7 @@
     regsub -all "(^|\n)\[^\n\]*: Additional NOP may be necessary to workaround Itanium processor A/B step errata" $text "" text
     regsub -all "(^|\n)\[^\n*\]*: Assembler messages:\[^\n\]*" $text "" text
+    regsub -all "(^|\n)can't find atom for N_GSYM stabs \[^\n\]* in \[^\n\]*" $text "" text
     return $text
--- gcc-4.2-20060822/gcc/testsuite/lib/    2006-08-23 18:33:56.000000000 -0400
+++ gcc-4.2-20060822/gcc/testsuite/lib/prune.exp        2006-08-23 18:41:28.000000000 -0400
@@ -43,6 +43,7 @@
     regsub -all "(^|\n)\[^\n\]*file path prefix \[^\n\]* never used" $text "" text
     regsub -all "(^|\n)\[^\n\]*linker input file unused since linking not done" $text "" text
+    regsub -all "(^|\n)can't find atom for N_GSYM stabs \[^\n\]* in \[^\n\]*" $text "" text
     #send_user "After:$text\n"
     return $text

...applied. You will also need to apply Geoff's proposed TImode patch
from Without
the TImode patch, libgfortran at least will be horribly broken since
it relies on libgcc being able to provide the TImode symbols for its
long long math operations. This will eliminate about 800 failures
from the gfortran testsuite. You need the patches above for ignoring
the linker warnings from ld64 to eliminate the remaining 40 some
false failures from the gfortran testsuite. The same is true for
libstdc++ which only really has 4 additional failures under -m64.
ps I have only patched the prune.exp to fix the builds of the
c,c++ and fortran languages. If you see massive failures for
any other language's testsuite, just look in the log for errors
of the form...

can't find atom for N_GSYM stabs

...if you seem them, the prune.exp being used for that
section of the testsuite needs a patch like those above.
Oh, when you do your make check from the top level of the 
build directory use this form of the command...

make -k check RUNTESTFLAGS='--target_board="unix{,-m64}"'

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