public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@cygnus.com>
To: Michael Alan Dorman <mdorman@law.miami.edu>
Cc: egcs@cygnus.com
Subject: Re: 1.0.3 pre-release available
Date: Mon, 27 Apr 1998 00:33:00 -0000	[thread overview]
Message-ID: <19980426221550.20521@dot.cygnus.com> (raw)
In-Reply-To: <ylfjzph8cbyx.fsf@law.miami.edu>

On Sun, Apr 26, 1998 at 09:03:34PM -0400, Michael Alan Dorman wrote:
> Ah, I just ran into the emacs issue yesterday.  It's great that it's
> fixed.  Our normal gcc-compiling-person will hopefully have the
> pre-release pacakged soon.

Do make sure emacs is fixed for you.  Cristian Gafton had reported
a problem, but not given details.  Later he reported that he could
not reproduce it.  It could have been the same problem as afflicted
ImageMagik, which would explain things, but it would be good to 
have this verified.

> Is there anyone that you know of consistently running the test suite
> against the compiler on Linux/Alpha?

Alexandre Oliva runs the tests regularly on a whole suite of systems,
including alpha-unknown-linux-gnu.  I run them myself often, though I
don't always do anything about failures immediately.  ;-)

I don't recall what the tstring.cc failure is.  I'm much worse about
following up on c++ failures vs c/f77 failures.

The only two I recall that I expect to fail are complex-5 and fp-cmp-1.


r~

  reply	other threads:[~1998-04-27  0:33 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
1998-04-26 18:03     ` Michael Alan Dorman
1998-04-27  0:33       ` Richard Henderson [this message]
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=19980426221550.20521@dot.cygnus.com \
    --to=rth@cygnus.com \
    --cc=egcs@cygnus.com \
    --cc=mdorman@law.miami.edu \
    /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).