From: Erik Mouw <J.A.K.Mouw@ITS.TUDelft.NL>
To: "J . A . Magallon" <jamagallon@able.es>
Cc: David <dllorens@lsi.uji.es>, linux-kernel@vger.kernel.org
Subject: Re: Posible bug in gcc
Date: Tue, 27 Feb 2001 11:56:50 +0100 [thread overview]
Message-ID: <20010227115649.H25658@arthur.ubicom.tudelft.nl> (raw)
In-Reply-To: <3A9A8489.224CF54C@inf.uji.es> <20010226233013.A2995@werewolf.able.es>
In-Reply-To: <20010226233013.A2995@werewolf.able.es>; from jamagallon@able.es on Mon, Feb 26, 2001 at 11:30:13PM +0100
On Mon, Feb 26, 2001 at 11:30:13PM +0100, J . A . Magallon wrote:
> On 02.26 David wrote:
> > I think I heve found a bug in gcc. I have tried both egcs 1.1.2 (gcc
> > 2.91.66) and gcc 2.95.2 versions.
>
> gcc2.95.2 is sane in irix6.2, irix6.5 and solaris7sparc.
>
> The optimizer is not in the common front-end ?
Yes and no. There is some common code in the optimiser, but each target
has its own optimisation tricks for which the code is not shared with
other targets.
Erik
--
J.A.K. (Erik) Mouw, Information and Communication Theory Group, Department
of Electrical Engineering, Faculty of Information Technology and Systems,
Delft University of Technology, PO BOX 5031, 2600 GA Delft, The Netherlands
Phone: +31-15-2783635 Fax: +31-15-2781843 Email: J.A.K.Mouw@its.tudelft.nl
WWW: http://www-ict.its.tudelft.nl/~erik/
prev parent reply other threads:[~2001-02-27 11:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-26 16:30 Posible bug in gcc David
2001-02-26 17:15 ` Alan Cox
2001-02-26 17:33 ` Jakub Jelinek
2001-02-26 18:02 ` Alan Cox
2001-02-26 18:02 ` Richard B. Johnson
2001-02-27 19:50 ` Ville Herva
2001-02-26 21:03 ` J . A . Magallon
2001-02-26 20:53 ` David Relson
2001-02-26 22:30 ` J . A . Magallon
2001-02-27 10:56 ` Erik Mouw [this message]
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=20010227115649.H25658@arthur.ubicom.tudelft.nl \
--to=j.a.k.mouw@its.tudelft.nl \
--cc=dllorens@lsi.uji.es \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
/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 NNTP newsgroup(s).