Re: gcc 3.4.0 testsuite gives over 5000 g++ errors

Re: gcc 3.4.0 testsuite gives over 5000 g++ errors

[Paul C. Leopardi]

Hi,
I checked versions as you suggested.
runtest -V
Expect version is       5.38.0
Tcl version is          8.4
Framework version is    1.4.3

I also rebuilt gcc 3.4.0 and re-ran the tests.
http://gcc.gnu.org/ml/gcc-testresults/2004-05/msg00137.html

I don't understand why the heading is "Results for 3.3.2 20031216 (prerelease) 
(SuSE Linux) testsuite on x86_64-suse-linux-gnu". I thought I was testing 
3.4.0? The test results themselves say, "LAST_UPDATED: Obtained from CVS: 
-rgcc_3_4_0_release".

Anyway, the result is about the same. Over 5000 g++ errors. 

I must have something configured wrong. What could it be?
Thanks

On Monday 03 May 2004 09:48, llewelly@xmission.com wrote:
> Re: gcc 3.4.0 testsuit gives over 5000 g++ errors
>
> From:
> llewelly@xmission.com
>
> "Paul C. Leopardi" <leopardi@bigpond.net.au> writes:
> > Hi all,
> > I've run the gcc test suite for the first time today, for gcc 3.4.0.
> > See http://gcc.gnu.org/ml/gcc-testresults/2004-05/msg00080.html
> > There were over 5000 g++ errors. With this many errors, I must have
> > configured something wrong. Where do I start in diagnosing the problem?
>
> Double-check your dejagnu, tcl and expect versions. Unfortunately, I
>     can't find the required versions in the docs. :-(
>
> I have expect 5.38, tcl 8.3, and dejagnu 1.4.3 installed, and I had
>     no difficulties running the 3.4.0 testsuite on fbsd5.2 .
>
> The odd thing which strikes me is that you have 5000+ C++ failures,
>     but 2647 libstdc++ successes. If g++ can compile libstdc++ & test
>     cases correctly, why does it fail nearly all C++ core tests? I
>     don't know.

Re: gcc 3.4.0 testsuite gives over 5000 g++ errors

[llewelly]

"Paul C. Leopardi" <leopardi@bigpond.net.au> writes:

> Hi,
> I checked versions as you suggested.
> runtest -V
> Expect version is       5.38.0
> Tcl version is          8.4
> Framework version is    1.4.3
> 
> I also rebuilt gcc 3.4.0 and re-ran the tests.
> http://gcc.gnu.org/ml/gcc-testresults/2004-05/msg00137.html
> 
> I don't understand why the heading is "Results for 3.3.2 20031216
> (prerelease)

This is really strange. I guess the dejagnu is running you old g++
    3.3.2 instead of the g++ you just built. I can't imagine *why*,
    however. Maybe an alias is interfering?

> (SuSE Linux) testsuite on x86_64-suse-linux-gnu". I thought I was testing 
> 3.4.0? The test results themselves say, "LAST_UPDATED: Obtained from CVS: 
> -rgcc_3_4_0_release".
> 
> Anyway, the result is about the same. Over 5000 g++ errors. 
> 
> I must have something configured wrong. What could it be?
[snip]

Re: gcc 3.4.0 testsuite gives over 5000 g++ errors

[Paul C. Leopardi]

Hi,
Answers and many questions below.
Best regards

On Tuesday 04 May 2004 02:08, llewelly@xmission.com wrote:
> "Paul C. Leopardi" <leopardi@bigpond.net.au> writes:
> > Hi,
> > I checked versions as you suggested.
> > runtest -V
> > Expect version is       5.38.0
> > Tcl version is          8.4
> > Framework version is    1.4.3
> >
> > I also rebuilt gcc 3.4.0 and re-ran the tests.
> > http://gcc.gnu.org/ml/gcc-testresults/2004-05/msg00137.html
> >
> > I don't understand why the heading is "Results for 3.3.2 20031216
> > (prerelease)
>
> This is really strange. I guess the dejagnu is running you old g++
>     3.3.2 instead of the g++ you just built. I can't imagine *why*,
>     however. Maybe an alias is interfering?

I tried the test suite again, after renaming /usr/local/bin 
to /usr/local/bin.old, and the test used /usr/bin/g++ this time.

		=== g++ Summary ===

# of expected passes		8454
# of unexpected failures	1404
# of unexpected successes	7
# of expected failures		61
# of unresolved testcases	15
# of untested testcases		30
# of unsupported tests		68
/usr/bin/g++ version 3.3.2 20031216 (prerelease) (SuSE Linux)

It turns out that I had colorgcc installed and the SuSE rpm had put links 
in /usr/local/bin from eg g++ to colorgcc.

I uninstalled colorgcc, renamed gcc-3.4.0.obj and ran configure and "make 
bootstrap" in a fresh directory, then ran "make -k check" again.

                === g++ Summary ===

# of expected passes            8455
# of unexpected failures        1403
# of unexpected successes       7
# of expected failures          61
# of unresolved testcases       15
# of untested testcases         30
# of unsupported tests          68
/usr/bin/g++ version 3.3.2 20031216 (prerelease) (SuSE Linux)

I think the build must have failed in some cryptic way. 
The output from "make bootstrap" is 12.9MB in size! How do I check it to see 
whether it succeeded? I thought that if it went all the way to the end it 
must have succeeded? No?
Where does g++ get built to? What file am I looking for?
How does runtest know where to find g++?
Sorry for all the questions. I am such a noob. Maybe this is all documented 
somewhere?
Should I direct these questions to the main gcc mailing list, or one of the 
suse mailing lists?

> > (SuSE Linux) testsuite on x86_64-suse-linux-gnu". I thought I was testing
> > 3.4.0? The test results themselves say, "LAST_UPDATED: Obtained from CVS:
> > -rgcc_3_4_0_release".
> >
> > Anyway, the result is about the same. Over 5000 g++ errors.
> >
> > I must have something configured wrong. What could it be?
>
> [snip]

Re: gcc 3.4.0 testsuite gives over 5000 g++ errors

[llewelly]

"Paul C. Leopardi" <leopardi@bigpond.net.au> writes:

> Hi,
> Answers and many questions below.
> Best regards
> 
> On Tuesday 04 May 2004 02:08, llewelly@xmission.com wrote:
> > "Paul C. Leopardi" <leopardi@bigpond.net.au> writes:
> > > Hi,
> > > I checked versions as you suggested.
> > > runtest -V
> > > Expect version is       5.38.0
> > > Tcl version is          8.4
> > > Framework version is    1.4.3
> > >
> > > I also rebuilt gcc 3.4.0 and re-ran the tests.
> > > http://gcc.gnu.org/ml/gcc-testresults/2004-05/msg00137.html
> > >
> > > I don't understand why the heading is "Results for 3.3.2 20031216
> > > (prerelease)
> >
> > This is really strange. I guess the dejagnu is running you old g++
> >     3.3.2 instead of the g++ you just built. I can't imagine *why*,
> >     however. Maybe an alias is interfering?
> 
> I tried the test suite again, after renaming /usr/local/bin 
> to /usr/local/bin.old, and the test used /usr/bin/g++ this time.
> 
> 		=== g++ Summary ===
> 
> # of expected passes		8454
> # of unexpected failures	1404
> # of unexpected successes	7
> # of expected failures		61
> # of unresolved testcases	15
> # of untested testcases		30
> # of unsupported tests		68
> /usr/bin/g++ version 3.3.2 20031216 (prerelease) (SuSE Linux)
> 
> It turns out that I had colorgcc installed and the SuSE rpm had put links 
> in /usr/local/bin from eg g++ to colorgcc.

I haven't had colorgcc installed on any machine I own for over 3
    years, so I had totally forgotten about it. But this seems to be
    only part of the problem; it shouldn't have been using
    /usr/local/bin/g++ in the first place.

> 
> I uninstalled colorgcc, renamed gcc-3.4.0.obj and ran configure and "make 
> bootstrap" in a fresh directory, then ran "make -k check" again.
> 
>                 === g++ Summary ===
> 
> # of expected passes            8455
> # of unexpected failures        1403
> # of unexpected successes       7
> # of expected failures          61
> # of unresolved testcases       15
> # of untested testcases         30
> # of unsupported tests          68
> /usr/bin/g++ version 3.3.2 20031216 (prerelease) (SuSE Linux)

This is completely mindboggling. Unless you have colorgcc installed in
    /usr/bin too?

> 
> I think the build must have failed in some cryptic way. 
> The output from "make bootstrap" is 12.9MB in size!

Maybe I'm jumping at shadows, but that sounds a little large ... I
    have  7028873 bytes (< 7MB) for the output of make boostrap-lean
    of 3.4.0 (c, objc, c++, java, f77) on i686-freeBSD5.2 .

> How do I check it to see 
> whether it succeeded? I thought that if it went all the way to the end it 
> must have succeeded?

I still think it is more likely that something went wrong with 
    make check than with make bootstrap. Remember, almost all of the
    libstdc++ tests succeed, and those use the 3.4.0 you just
    built. So I *think* the newly built g++ binary is ok. It just isn't
    getting run by 'make check'.

> No?
> Where does g++ get built to?

It should be in objdir/gcc . 

> What file am I looking for?
> How does runtest know where to find g++?

I don't know. I seem to lack dejagnu info files for some reason. Could
    you try aliasing 'runtest' to 'runtest -v' ?

> Sorry for all the questions. I am such a noob. Maybe this is all documented 
> somewhere?
> Should I direct these questions to the main gcc mailing list, or one of the 
> suse mailing lists?
> 
> > > (SuSE Linux) testsuite on x86_64-suse-linux-gnu". I thought I was testing
> > > 3.4.0? The test results themselves say, "LAST_UPDATED: Obtained from CVS:
> > > -rgcc_3_4_0_release".
> > >
> > > Anyway, the result is about the same. Over 5000 g++ errors.
> > >
> > > I must have something configured wrong. What could it be?
> >
> > [snip]

Re: gcc 3.4.0 testsuite gives over 5000 g++ errors

[Paul C. Leopardi]

[-- Attachment #1: Type: text/plain, Size: 2424 bytes --]

Hi again, Answers below. Best regards
On Tuesday 04 May 2004 15:43, llewelly@xmission.com wrote:
> "Paul C. Leopardi" <leopardi@bigpond.net.au> writes:
> > It turns out that I had colorgcc installed and the SuSE rpm had put links
> > in /usr/local/bin from eg g++ to colorgcc.
>
> I haven't had colorgcc installed on any machine I own for over 3
>     years, so I had totally forgotten about it. But this seems to be
>     only part of the problem; it shouldn't have been using
>     /usr/local/bin/g++ in the first place.
Yes.

> > I uninstalled colorgcc, renamed gcc-3.4.0.obj and ran configure and "make
> > bootstrap" in a fresh directory, then ran "make -k check" again.
> >
> >                 === g++ Summary ===
> >
> > # of expected passes            8455
> > # of unexpected failures        1403
> > # of unexpected successes       7
> > # of expected failures          61
> > # of unresolved testcases       15
> > # of untested testcases         30
> > # of unsupported tests          68
> > /usr/bin/g++ version 3.3.2 20031216 (prerelease) (SuSE Linux)
>
> This is completely mindboggling. Unless you have colorgcc installed in
>     /usr/bin too?
No.

> > I think the build must have failed in some cryptic way.
> > The output from "make bootstrap" is 12.9MB in size!
>
> Maybe I'm jumping at shadows, but that sounds a little large ... I
>     have  7028873 bytes (< 7MB) for the output of make boostrap-lean
>     of 3.4.0 (c, objc, c++, java, f77) on i686-freeBSD5.2 .
>
> > How do I check it to see
> > whether it succeeded? I thought that if it went all the way to the end it
> > must have succeeded?
>
> I still think it is more likely that something went wrong with
>     make check than with make bootstrap. Remember, almost all of the
>     libstdc++ tests succeed, and those use the 3.4.0 you just
>     built. So I *think* the newly built g++ binary is ok. It just isn't
>     getting run by 'make check'.
>
> > No?
> > Where does g++ get built to?
>
> It should be in objdir/gcc .
>
> > What file am I looking for?
The file g++ is in gcc-3.4.0-obj/gcc

> > How does runtest know where to find g++?
>
> I don't know. I seem to lack dejagnu info files for some reason. Could
>     you try aliasing 'runtest' to 'runtest -v' ?
I have done so and run "make -k check" again. I've attached the diff. In 
summary, nothing has chaned and runtest -v gives no extra info.

Should I ask on the dejagnu list?


[-- Attachment #2: make-k-check.1.2.diff --]
[-- Type: text/x-diff, Size: 13776 bytes --]

--- make-k-check.1.out	2004-05-04 11:56:26.000000000 +1000
+++ make-k-check.2.out	2004-05-05 00:15:18.040161576 +1000
@@ -1,9 +1,4 @@
 make[1]: Entering directory `/home/leopardi/Documents/src/gcc/gcc-3.4.0-obj/gcc'
-Making a new config file...
-echo "set tmpdir /home/leopardi/Documents/src/gcc/gcc-3.4.0-obj/gcc/testsuite" >> ./tmp0
-test -d testsuite || mkdir testsuite
-rm -f testsuite/site.exp
-sed '/set tmpdir/ s|testsuite|testsuite|' < site.exp > testsuite/site.exp
 (rootme=`${PWDCMD-pwd}`; export rootme; \
 srcdir=`cd ../../gcc-3.4.0/gcc; ${PWDCMD-pwd}` ; export srcdir ; \
 cd testsuite; \
@@ -12,7 +7,7 @@
    TCL_LIBRARY=`cd .. ; cd ../../gcc-3.4.0/gcc/../tcl/library ; ${PWDCMD-pwd}` ; \
     export TCL_LIBRARY ; fi ; \
 runtest --tool gcc )
-Test Run By leopardi on Tue May  4 11:11:56 2004
+Test Run By leopardi on Tue May  4 23:29:13 2004
 Native configuration is x86_64-suse-linux-gnu
 
 		=== gcc tests ===
@@ -90,7 +85,7 @@
    TCL_LIBRARY=`cd .. ; cd ../../gcc-3.4.0/gcc/../tcl/library ; ${PWDCMD-pwd}` ; \
     export TCL_LIBRARY ; fi ; \
 runtest --tool g++ )
-Test Run By leopardi on Tue May  4 11:24:33 2004
+Test Run By leopardi on Tue May  4 23:42:32 2004
 Native configuration is x86_64-suse-linux-gnu
 
 		=== g++ tests ===
@@ -1033,6 +1028,7 @@
 FAIL: g++.dg/template/nontype3.C integral or enumeration (test for errors, line 30)
 FAIL: g++.dg/template/nontype3.C constant-expression (test for errors, line 33)
 FAIL: g++.dg/template/nontype3.C constant-expression (test for errors, line 36)
+FAIL: g++.dg/template/nontype4.C (test for excess errors)
 FAIL: g++.dg/template/nontype5.C (test for excess errors)
 FAIL: g++.dg/template/nontype6.C  (test for errors, line 15)
 FAIL: g++.dg/template/nontype6.C  (test for errors, line 15)
@@ -1579,8 +1575,8 @@
 
 		=== g++ Summary ===
 
-# of expected passes		8455
-# of unexpected failures	1403
+# of expected passes		8454
+# of unexpected failures	1404
 # of unexpected successes	7
 # of expected failures		61
 # of unresolved testcases	15
@@ -1597,7 +1593,7 @@
    TCL_LIBRARY=`cd .. ; cd ../../gcc-3.4.0/gcc/../tcl/library ; ${PWDCMD-pwd}` ; \
     export TCL_LIBRARY ; fi ; \
 runtest --tool g77 )
-Test Run By leopardi on Tue May  4 11:35:34 2004
+Test Run By leopardi on Tue May  4 23:53:51 2004
 Native configuration is x86_64-suse-linux-gnu
 
 		=== g77 tests ===
@@ -1630,7 +1626,7 @@
    TCL_LIBRARY=`cd .. ; cd ../../gcc-3.4.0/gcc/../tcl/library ; ${PWDCMD-pwd}` ; \
     export TCL_LIBRARY ; fi ; \
 runtest --tool objc )
-Test Run By leopardi on Tue May  4 11:37:02 2004
+Test Run By leopardi on Tue May  4 23:55:19 2004
 Native configuration is x86_64-suse-linux-gnu
 
 		=== objc tests ===
@@ -1664,8 +1660,6 @@
 make[1]: Leaving directory `/home/leopardi/Documents/src/gcc/gcc-3.4.0-obj/intl'
 make[1]: Entering directory `/home/leopardi/Documents/src/gcc/gcc-3.4.0-obj/libiberty'
 make[2]: Entering directory `/home/leopardi/Documents/src/gcc/gcc-3.4.0-obj/libiberty/testsuite'
-gcc -DHAVE_CONFIG_H -g -O2 -I.. -I../../../gcc-3.4.0/libiberty/testsuite/../../include  -o test-demangle \
-	../../../gcc-3.4.0/libiberty/testsuite/test-demangle.c ../libiberty.a
 ./test-demangle < ../../../gcc-3.4.0/libiberty/testsuite/demangle-expected
 ./test-demangle: 745 tests, 0 failures
 make[2]: Leaving directory `/home/leopardi/Documents/src/gcc/gcc-3.4.0-obj/libiberty/testsuite'
@@ -1704,7 +1698,6 @@
 touch testsuite_wchar_t
 make -j1 check-DEJAGNU check-local
 make[3]: Entering directory `/home/leopardi/Documents/src/gcc/gcc-3.4.0-obj/x86_64-suse-linux/libstdc++-v3/testsuite'
-Making a new site.exp file...
 srcdir=`CDPATH="${ZSH_VERSION+.}:" && cd ../../../../gcc-3.4.0/libstdc++-v3/testsuite && pwd`; export srcdir; \
 EXPECT=expect; export EXPECT; \
 runtest=runtest; \
@@ -1714,7 +1707,7 @@
   done; \
 else echo "WARNING: could not find \`runtest'" 1>&2; :;\
 fi
-Test Run By leopardi on Tue May  4 11:37:59 2004
+Test Run By leopardi on Tue May  4 23:56:17 2004
 Native configuration is x86_64-suse-linux-gnu
 
 		=== libstdc++ tests ===
@@ -1843,53 +1836,53 @@
          call date (ctim)
               ^
 Intrinsic `DATE', invoked at (^), known to be non-Y2K-compliant [info -f g77 M Y2KBAD]
-1 GNU libU77 test at: Tue May  4 11:48:54 2004
+1 GNU libU77 test at: Wed May  5 00:07:22 2004
 
  Logical units 5 and 6 correspond (FNUM) to Unix i/o units   0,   1
  Command-line arguments:  0
  Arg  0 is: ./a.out
  and 6 isn't a tty device (ISATTY)
- Process id (GETPID):       2857
+ Process id (GETPID):      12575
  User id (GETUID):        500
  Group id (GETGID):        100
  If you have the `id' program, the following call
  of SYSTEM should agree with the above:
   uid=500(leopardi) gid=100(users) groups=14(uucp),16(dialout),17(audio),33(video),42(trusted),100(users)
 ./a.out: No such file or directory
- Login name (GETLOG):  
+ Login name (GETLOG): leopardi
  Login name (GETENV of LOGNAME): leopardi
  UMASK returns 18
- FDATE returns: Tue May  4 11:48:54 2004
- CALL FDATE returns: Tue May  4 11:48:54 2004
- LTIME returns:  54  48  11   4   4 104   2 124   0
- GMTIME returns:  54  48   1   4   4 104   2 124   0
- SYSTEM_CLOCK returns:  16601070 100 2147483647
- DATE_AND_TIME returns: 20040504 114854.010 +1000  2004 5 4 600 11 48 54 10
+ FDATE returns: Wed May  5 00:07:22 2004
+ CALL FDATE returns: Wed May  5 00:07:22 2004
+ LTIME returns:  22   7   0   5   4 104   3 125   0
+ GMTIME returns:  22   7  14   4   4 104   2 124   0
+ SYSTEM_CLOCK returns:  21033140 100 2147483647
+ DATE_AND_TIME returns: 20040505 000722.333 +1000  2004 5 5 600 0 7 22 333
  Sleeping for 1 second (SLEEP) ...
- Elapsed total, user, system time (ETIME):      0.002     0.001     0.001
+ Elapsed total, user, system time (ETIME):      0.001     0.000     0.001
  Looping until clock ticks at least once...
  Differences in total, user, system time (DTIME):      0.001     0.001     0.000
- Elapsed total, user, system time (ETIME):      0.003     0.002     0.001
- (Clock-tick detected after  210 1K loops.)
- IDATE (date,month,year):  4 5 2004
- ... and the VXT version (month,date,year):  5 4 4
- DATE (dd-mmm-yy):  4-May-04
- ITIME (hour,minutes,seconds):  11 48 55
- TIME: 11:48:55
- SECNDS(0.0) returns:   42535.
- SECOND returns:   0.00299800001
- CALL SECOND returns:   0.00299800001
+ Elapsed total, user, system time (ETIME):      0.002     0.001     0.001
+ (Clock-tick detected after  209 1K loops.)
+ IDATE (date,month,year):  5 5 2004
+ ... and the VXT version (month,date,year):  5 5 4
+ DATE (dd-mmm-yy):  5-May-04
+ ITIME (hour,minutes,seconds):  0 7 23
+ TIME: 00:07:23
+ SECNDS(0.0) returns:   443.
+ SECOND returns:   0.00199800008
+ CALL SECOND returns:   0.00199800008
  Current directory is "/home/leopardi/Documents/src/gcc/gcc-3.4.0-obj/x86_64-suse-linux/libf2c/libU77"
  Host name is linfinit
  Creating file "foo" for testing...
-   with stat array  774 245156 33206 1 500 100 0 2 1083635335 1083635335
- 1083635335 4096 8
+   with stat array  774 245199 33206 1 500 100 0 2 1083679643 1083679643
+ 1083679643 4096 8
  The current error number is:   2 and the corresponding message is:
  No such file or directory
  This is sent to stderr prefixed by the program name
  MCLOCK returns  0
  MCLOCK8 returns  0
- CPU_TIME returns   0.00299800001
+ CPU_TIME returns   0.00199800008
  You should see exit status 1
 make[2]: [check] Error 1 (ignored)
 rm -f a.out
@@ -1912,7 +1905,6 @@
 make[2]: Entering directory `/home/leopardi/Documents/src/gcc/gcc-3.4.0-obj/x86_64-suse-linux/libffi/testsuite'
 make  check-DEJAGNU
 make[3]: Entering directory `/home/leopardi/Documents/src/gcc/gcc-3.4.0-obj/x86_64-suse-linux/libffi/testsuite'
-Making a new site.exp file...
 srcdir=`cd ../../../../gcc-3.4.0/libffi/testsuite && pwd`; export srcdir; \
 EXPECT=`if [ -f ../../expect/expect ] ; then echo ../../expect/expect ; else echo expect ; fi`; export EXPECT; \
 runtest=`if [ -f ../../../../gcc-3.4.0/libffi/../dejagnu/runtest ] ; then echo ../../../../gcc-3.4.0/libffi/../dejagnu/runtest ; else echo runtest; fi`; \
@@ -1921,7 +1913,7 @@
 else echo "WARNING: could not find \`runtest'" 1>&2; :;\
 fi
 WARNING: Couldn't find tool init file
-Test Run By leopardi on Tue May  4 11:48:55 2004
+Test Run By leopardi on Wed May  5 00:07:23 2004
 Native configuration is x86_64-suse-linux-gnu
 
 		=== libffi tests ===
@@ -2211,7 +2203,6 @@
 make[2]: Entering directory `/home/leopardi/Documents/src/gcc/gcc-3.4.0-obj/x86_64-suse-linux/libjava/testsuite'
 make  check-DEJAGNU
 make[3]: Entering directory `/home/leopardi/Documents/src/gcc/gcc-3.4.0-obj/x86_64-suse-linux/libjava/testsuite'
-Making a new site.exp file...
 srcdir=`cd ../../../../gcc-3.4.0/libjava/testsuite && pwd`; export srcdir; \
 EXPECT=`if [ -f ../../expect/expect ] ; then echo ../../expect/expect ; else echo expect ; fi`; export EXPECT; \
 runtest="`if [ -f ../../../../gcc-3.4.0/libjava/../dejagnu/runtest ] ; then echo ../../../../gcc-3.4.0/libjava/../dejagnu/runtest ; else echo runtest; fi` INTERPRETER=yes"; \
@@ -2219,7 +2210,7 @@
   $runtest --tool libjava --srcdir $srcdir ; \
 else echo "WARNING: could not find \`runtest'" 1>&2; :;\
 fi
-Test Run By leopardi on Tue May  4 11:49:06 2004
+Test Run By leopardi on Wed May  5 00:07:35 2004
 Native configuration is x86_64-suse-linux-gnu
 
 		=== libjava tests ===
@@ -2278,15 +2269,11 @@
 make[2]: Nothing to be done for `check'.
 make[2]: Leaving directory `/home/leopardi/Documents/src/gcc/gcc-3.4.0-obj/x86_64-suse-linux/boehm-gc/include'
 make[2]: Entering directory `/home/leopardi/Documents/src/gcc/gcc-3.4.0-obj/x86_64-suse-linux/boehm-gc'
-/home/leopardi/Documents/src/gcc/gcc-3.4.0-obj/gcc/xgcc -B/home/leopardi/Documents/src/gcc/gcc-3.4.0-obj/gcc/ -B/opt/gcc34/x86_64-suse-linux/bin/ -B/opt/gcc34/x86_64-suse-linux/lib/ -isystem /opt/gcc34/x86_64-suse-linux/include -isystem /opt/gcc34/x86_64-suse-linux/sys-include -DGC_LINUX_THREADS=1 -D_REENTRANT=1 -DTHREAD_LOCAL_ALLOC=1 -DSILENT=1 -DNO_SIGNALS=1 -DALL_INTERIOR_POINTERS=1 -DJAVA_FINALIZATION=1 -DGC_GCJ_SUPPORT=1 -DATOMIC_UNCOLLECTABLE=1  -I. -I../../../gcc-3.4.0/boehm-gc  -I/home/leopardi/Documents/src/gcc/gcc-3.4.0/boehm-gc/include  -O2 -g -O2 -fexceptions -I././targ-include -I./../../../gcc-3.4.0/boehm-gc/./libc/include -O2 -g -O2 -c ../../../gcc-3.4.0/boehm-gc/tests/test.c
-/bin/sh ./libtool --mode=link /home/leopardi/Documents/src/gcc/gcc-3.4.0-obj/gcc/xgcc -B/home/leopardi/Documents/src/gcc/gcc-3.4.0-obj/gcc/ -B/opt/gcc34/x86_64-suse-linux/bin/ -B/opt/gcc34/x86_64-suse-linux/lib/ -isystem /opt/gcc34/x86_64-suse-linux/include -isystem /opt/gcc34/x86_64-suse-linux/sys-include -fexceptions -I././targ-include -I./../../../gcc-3.4.0/boehm-gc/./libc/include -O2 -g -O2  -o gctest -shared-libgcc test.o ./libgcjgc.la -lpthread -ldl 
-/home/leopardi/Documents/src/gcc/gcc-3.4.0-obj/gcc/xgcc -B/home/leopardi/Documents/src/gcc/gcc-3.4.0-obj/gcc/ -B/opt/gcc34/x86_64-suse-linux/bin/ -B/opt/gcc34/x86_64-suse-linux/lib/ -isystem /opt/gcc34/x86_64-suse-linux/include -isystem /opt/gcc34/x86_64-suse-linux/sys-include -fexceptions -I././targ-include -I./../../../gcc-3.4.0/boehm-gc/./libc/include -O2 -g -O2 -o .libs/gctest -shared-libgcc test.o  ./.libs/libgcjgc.so -lpthread -ldl -Wl,--rpath -Wl,/opt/gcc34/lib64/../lib64
-creating gctest
 make "AR_FLAGS=rc" "CC_FOR_BUILD=gcc" "CFLAGS=-O2 -g -O2" "CXXFLAGS=-g -O2 -D_GNU_SOURCE" "CFLAGS_FOR_BUILD=" "CFLAGS_FOR_TARGET=-O2 -g -O2" "INSTALL=/usr/bin/install -c" "INSTALL_DATA=/usr/bin/install -c -m 644" "INSTALL_PROGRAM=/usr/bin/install -c" "INSTALL_SCRIPT=/usr/bin/install -c" "LDFLAGS=" "LIBCFLAGS=-O2 -g -O2" "LIBCFLAGS_FOR_TARGET=-O2 -g -O2" "MAKE=make" "MAKEINFO=makeinfo --split-size=5000000  " "PICFLAG=" "PICFLAG_FOR_TARGET=" "SHELL=/bin/sh" "EXPECT=expect" "RUNTEST=runtest" "RUNTESTFLAGS=" "exec_prefix=/opt/gcc34" "infodir=/opt/gcc34/share/info" "libdir=/opt/gcc34/lib64" "prefix=/opt/gcc34" "tooldir=/opt/gcc34/x86_64-suse-linux" "AR=ar" "AS=as" "CC=/home/leopardi/Documents/src/gcc/gcc-3.4.0-obj/gcc/xgcc -B/home/leopardi/Documents/src/gcc/gcc-3.4.0-obj/gcc/ -B/opt/gcc34/x86_64-suse-linux/bin/ -B/opt/gcc34/x86_64-suse-linux/lib/ -isystem /opt/gcc34/x86_64-suse-linux/include -isystem /opt/gcc34/x86_64-suse-linux/sys-include" "CXX=/home/leopardi/Documents/src/gcc/gcc-3.4.0-obj/gcc/g++ -B/home/leopardi/Documents/src/gcc/gcc-3.4.0-obj/gcc/ -nostdinc++ -nostdinc++ -I/home/leopardi/Documents/src/gcc/gcc-3.4.0-obj/x86_64-suse-linux/libstdc++-v3/include/x86_64-suse-linux -I/home/leopardi/Documents/src/gcc/gcc-3.4.0-obj/x86_64-suse-linux/libstdc++-v3/include -I/home/leopardi/Documents/src/gcc/gcc-3.4.0/libstdc++-v3/libsupc++ -I/home/leopardi/Documents/src/gcc/gcc-3.4.0/libstdc++-v3/libsupc++ -I/home/leopardi/Documents/src/gcc/gcc-3.4.0/libstdc++-v3/include/backward -I/home/leopardi/Documents/src/gcc/gcc-3.4.0/libstdc++-v3/testsuite -L/home/leopardi/Documents/src/gcc/gcc-3.4.0-obj/x86_64-suse-linux/libstdc++-v3/src -L/home/leopardi/Documents/src/gcc/gcc-3.4.0-obj/x86_64-suse-linux/libstdc++-v3/src/.libs -B/opt/gcc34/x86_64-suse-linux/bin/ -B/opt/gcc34/x86_64-suse-linux/lib/ -isystem /opt/gcc34/x86_64-suse-linux/include -isystem /opt/gcc34/x86_64-suse-linux/sys-include" "LD=ld" "LIBCFLAGS=-O2 -g -O2" "NM=nm" "PICFLAG=" "RANLIB=ranlib" "DESTDIR=" check-TESTS
 make[3]: Entering directory `/home/leopardi/Documents/src/gcc/gcc-3.4.0-obj/x86_64-suse-linux/boehm-gc'
 Switched to incremental mode
 Emulating dirty bits with mprotect/signals
-Segfault at 0x7fbfffd8e0
+Segfault at 0x2a95fadcb8
 Unexpected bus error or segmentation fault
 FAIL: gctest
 ===================

Re: gcc 3.4.0 testsuite gives over 5000 g++ errors

[Paul C. Leopardi]

Oops, I had 
"alias runtest 'runtest -v'" instead of 
"alias runtest='runtest -v'"

I'm running "make -k check" again, with
"alias runtest='runtest -v -v -v'"

Re: gcc 3.4.0 testsuite gives over 5000 g++ errors

[Claudio Bley]

Hi.

On Wed, May 05, 2004 at 12:47:27AM +1000, Paul C. Leopardi wrote:
> Oops, I had 
> "alias runtest 'runtest -v'" instead of 
> "alias runtest='runtest -v'"
> 
> I'm running "make -k check" again, with
> "alias runtest='runtest -v -v -v'"

Aliases are a shell mechanism, and hence are not exported to subshells or 
commands since expansion takes place before a command is executed. And they 
are also not expanded in non-interactive shells by default.

(at least that's the case for bash)

So, to make sure that "runtest -v -v -v" is called rather than just `runtest' 
better make a little sh script called `runtest' and place it somewhere in your 
PATH before the real runtest program; e.g.:

#!/bin/sh

echo "( runtest -v -v -v )" 1>&2
/usr/bin/runtest -v -v -v "$@"

-- 
Claudio