public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jim Wilson <wilson@cygnus.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] gcc -O2
Date: Mon, 02 Oct 2000 21:05:22 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678205534@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205531@msgid-missing>

All optimizing compilers have bugs.  You shouldn't panic when you find one.
The -O2 option is definitely usable.  Entire linux distributions have been
built with it.

There are some known problems with the C++ support in the 000216 release.
There was a lot of C++ front end development work happening at the time, and
we ended up with an FSF gcc snapshot that has a few instabilities in the C++
front end.  Otherwise, the release has held up very well.  There haven't been
very many problems with it.

Bug reports sent here are OK.  Bug reports sent to the usual FSF addresses
are OK, if you make it clear that you are using one of the unofficial releases
that the ia64-linux project is using.

There is a new toolchain release that you can try if you are interested.
I expect that the next series of linux distributions will use this new
toolchain.  It is located on ftp.cygnus.com in pub/ia64-linux.

I am not too interested in bug reports against the old toolchain at this point,
but I will help if I can.

Jim


  parent reply	other threads:[~2000-10-02 21:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-02 17:20 [Linux-ia64] gcc -O2 Steve Tynor
2000-10-02 20:37 ` H . J . Lu
2000-10-02 20:44 ` Steve Tynor
2000-10-02 21:05 ` Jim Wilson [this message]
2000-10-02 21:14 ` Steve Tynor
2000-10-02 21:27 ` Jim Wilson

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=marc-linux-ia64-105590678205534@msgid-missing \
    --to=wilson@cygnus.com \
    --cc=linux-ia64@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