From: Steve Tynor <tynor@atlanta.twr.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] gcc -O2
Date: Mon, 02 Oct 2000 17:20:09 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205531@msgid-missing> (raw)
I'm using
# gcc -v
Reading specs from /usr/lib/gcc-lib/ia64-cygnus-linux/2.9-ia64-000216-final/specs
gcc version 2.9-ia64-000216-final
as bundled in Turbolinux 0823
# uname -a
Linux impromptu 2.4.0test7-000823-42 #1 Sat Aug 26 16:31:32 PDT 2000 ia64 unknown
I've diagnosed a seg fault that seems to stem from a bad optimization by
gcc -O2. I can't find any FAQ that discusses known problems with the
ia64 gcc. Is there one? Is -O2 considered generally usable? or is it
well known that one ought to avoid it in this release? How 'bout
vanilla -O? (my particular test case works OK with -O but it's hardly an
exhaustive test...).
Where should I direct gcc bug reports -- on this list, or to the general
gcc bug reporting mechanism (a query on GNATS on gcc.gnu.org shows no
matches on the search string "ia64"... Mmmm.... :-)).
Ought I avoid gcc and skip directly to the SGI sgicc?
Steve
next reply other threads:[~2000-10-02 17:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-02 17:20 Steve Tynor [this message]
2000-10-02 20:37 ` [Linux-ia64] gcc -O2 H . J . Lu
2000-10-02 20:44 ` Steve Tynor
2000-10-02 21:05 ` Jim Wilson
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-105590678205531@msgid-missing \
--to=tynor@atlanta.twr.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.