From: Bill Nottingham <notting@redhat.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: gcc bug (2.9-ia64-000216-final)
Date: Tue, 03 Oct 2000 00:26:15 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205538@msgid-missing> (raw)
Steve Tynor (tynor@atlanta.twr.com) said:
> Can someone verify that this bug is fixed in the latest toolchain?
Works for me. A quick glance at the code makes me think that building
with -fno-optimize-sibling-calls will work around it for now.
Bill
next reply other threads:[~2000-10-03 0:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-03 0:26 Bill Nottingham [this message]
2000-10-03 0:46 ` [Linux-ia64] Re: gcc bug (2.9-ia64-000216-final) Steve Tynor
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-105590678205538@msgid-missing \
--to=notting@redhat.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