public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: hjstein@bfr.co.il (Harvey J. Stein)
To: Richard Henderson <rth@cygnus.com>, egcs@cygnus.com
Cc: hjstein@blinky.bfr.co.il
Subject: Re: egcs-1.0 alphaev56-unknown-linux-gnulibc1 test results
Date: Wed, 10 Dec 1997 02:27:00 -0000	[thread overview]
Message-ID: <m2btypbiir.fsf@blinky.bfr.co.il> (raw)
In-Reply-To: <19971209105944.41892@dot.cygnus.com>

Richard Henderson <rth@cygnus.com> writes:

> Copy the gcc/testsuite directory out somethere, make sure gcc 2.7.2
> is the gcc on your path, and do "runtest --tool=gcc".  I did this a
> while ago -- the results are fairly bad.
> 
> 
> > FAIL: gcc.c-torture/execute/960218-1.c execution,  -O0 
> 
> This one I don't see here.  Can you find this section in the gcc.log
> file and figure out what kind of failure?

   Executing on host: /home/hjstein/software/egcs-1.0-build/gcc/xgcc -B/home/hjstein/software/egcs-1.0-build/gcc/ /home/hjstein/software/egcs-1.0/gcc/testsuite/gcc.c-torture/execute/960218-1.c  -w  -O0    -lm  -o /tmp/960218-1.x   
   output is:
   /usr/bin/ld: Warning: size of symbol `glob' changed from 4 to 2900 in /lib/libc.so.6
   PASS: gcc.c-torture/execute/960218-1.c compilation,  -O0 
   FAIL: gcc.c-torture/execute/960218-1.c execution,  -O0 

I guess it looks more like a libc failure than an egcs failure - glob
is defined in libc!

-- 
Harvey J. Stein
Berger Financial Research
hjstein@bfr.co.il

  reply	other threads:[~1997-12-10  2:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-12-09  9:52 Harvey J. Stein
1997-12-09 10:59 ` Richard Henderson
1997-12-10  2:27   ` Harvey J. Stein [this message]
1997-12-10  2:49   ` Harvey J. Stein
1997-12-09 14:34 ` Toon Moene
1997-12-09 16:25   ` namelist patch [was egcs-1.0 alphaev56-unknown-linux-gnulibc1 test results] Richard Henderson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2btypbiir.fsf@blinky.bfr.co.il \
    --to=hjstein@bfr.co.il \
    --cc=egcs@cygnus.com \
    --cc=hjstein@blinky.bfr.co.il \
    --cc=rth@cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).