public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Toon Moene <toon@moene.indiv.nluug.nl>
To: Michael Alan Dorman <mdorman@law.miami.edu>
Cc: egcs@cygnus.com
Subject: Re: bug with asm statment in egcs-1.0.2
Date: Fri, 24 Apr 1998 06:54:00 -0000	[thread overview]
Message-ID: <9804241207.AA26253@moene.indiv.nluug.nl> (raw)
In-Reply-To: <ylfjemyom4fa.fsf@law.miami.edu>

Joe Buck <jbuck@synopsys.com> writes:

>> But the reason for 1.0.3 is to *quickly* get out a release that is
>> good enough to build Linux/Alpha.  We can't fix every bug in the
>> universe.

Michael Dorman:

>  Well, the porters for the AXP version of Debian GNU/Linux
>  has been using egcs as our primary compiler since 1.0
>  came out

[ ... ]

>  That leaves me curious as to what problems the RedHat
>  people are having that are considered sufficiently
>  showstopping to warrant forcing a new compiler release.

Although the 1.0.3 release will contain a bugfix for the Alpha, it  
is in the Fortran Frontend, and not Linux specific at all.

No, I suspect that the problems that have to be solved by 1.0.3 are  
entirely due to the i666, the architecture of the Beast (1/2 :-)

Toon.

  reply	other threads:[~1998-04-24  6:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-04-21 19:10 Peter Barada
1998-04-22  4:19 ` Jeffrey A Law
1998-04-22  8:31   ` H.J. Lu
1998-04-22 18:40     ` Jeffrey A Law
1998-04-23  2:49       ` Wolfram Gloger
1998-04-23 10:41         ` Joe Buck
1998-04-23 21:12           ` Michael Alan Dorman
1998-04-24  6:54             ` Toon Moene [this message]
1998-04-24 10:34               ` Jeffrey A Law
1998-04-23 13:31         ` Jeffrey A Law

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=9804241207.AA26253@moene.indiv.nluug.nl \
    --to=toon@moene.indiv.nluug.nl \
    --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).