From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: gcc bug
Date: Wed, 18 Jun 2003 19:00:58 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105596286528010@msgid-missing> (raw)
>>>>> On Tue, 17 Jun 2003 18:30:48 -0700, Umut Aymakoglu <umuta@us.ibm.com> said:
Umut> Hi -
Umut> Below is a small repro which shows the bug and the output that I get. Is
Umut> this a known bug? Any help will be appreciated.
Umut> The version of glibc : glibc-2/2/4-32.3
The linux-ia64 list is not really the right place for reporting GCC
bugs. Please see:
http://gcc.gnu.org/bugs.html
for how to report GCC bugs.
You didn't mention what compiler you were using. I tried your test
program quickly with gcc 3.2.3 and it worked fine for me.
--david
reply other threads:[~2003-06-18 19:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-105596286528010@msgid-missing \
--to=davidm@napali.hpl.hp.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