public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: Toon Moene <toon@moene.indiv.nluug.nl>
Cc: egcs@cygnus.com
Subject: Re: 1.0.3 pre-release available
Date: Sun, 26 Apr 1998 10:05:00 -0000	[thread overview]
Message-ID: <19439.893610195@hurl.cygnus.com> (raw)
In-Reply-To: <9804261449.AA17362@moene.indiv.nluug.nl>

  In message < 9804261449.AA17362@moene.indiv.nluug.nl >you write:
  > So there were Linux/Alpha problems ?  Shees, means that Joe was  
  > right after all - perhaps I missed it due to the ix86 advocates  
  > being so much more vocal (gives a whole new meaning to "devils  
  > advocate" :-)
There was a profiling problem and problems compiling ImageMagick
and emacs-20.2.  I've expanded on the "Alpha bugs" section in the
propsed release announcement :-)


  >                 === libstdc++ tests ===
  > 
  > FAIL: tstring.cc compilation
  > FAIL: tstring.cc -O compilation
Hmmm, this worries me a little.  Then again, maybe this has been
failing all along.


  > FAIL: gcc.c-torture/execute/960218-1.c execution,  -O0
The "glob" problem with the Linux C library.

  > FAIL: gcc.c-torture/execute/complex-5.c execution,  -O0
The usual complex failures.  

  > FAIL: gcc.c-torture/execute/ieee/fp-cmp-1.c execution,  -O0
Not sure.  This might be another case where the alpha needs
-mieee.  Dunno.

jeff

  reply	other threads:[~1998-04-26 10:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-04-26  0:01 Jeffrey A Law
1998-04-26  8:21 ` Toon Moene
1998-04-26 10:05   ` Jeffrey A Law [this message]
1998-04-26 18:03     ` Michael Alan Dorman
1998-04-27  0:33       ` Richard Henderson
1998-04-27  8:47         ` H.J. Lu
1998-04-26 12:45 ` H.J. Lu
1998-04-26 10:05   ` Jeffrey A Law
     [not found] ` <m0yTUQG-000598C.cygnus.egcs@ocean.lucon.org>
1998-04-26 21:56   ` Nathan Myers

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=19439.893610195@hurl.cygnus.com \
    --to=law@cygnus.com \
    --cc=egcs@cygnus.com \
    --cc=toon@moene.indiv.nluug.nl \
    /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).