public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: dennis@mds.rmit.edu.au
To: gcc-gnats@gcc.gnu.org
Subject: c++/7823: Itanium linux gcc 3.2 optimizer bug at -O2 level and above.
Date: Tue, 03 Sep 2002 20:16:00 -0000 [thread overview]
Message-ID: <20020904030929.20367.qmail@sources.redhat.com> (raw)
>Number: 7823
>Category: c++
>Synopsis: Itanium linux gcc 3.2 optimizer bug at -O2 level and above.
>Confidential: no
>Severity: critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Sep 03 20:16:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: Dennis B.
>Release: g++ (GCC) 3.2
>Organization:
>Environment:
RedHat Linux for Itanium.
kernel 2.4.18-e.0.2smp
glibc 2.2.5
HP Rx4610 quad Itanium machine.
>Description:
The little test case supplied produces an illegal
instruction error when using -O2 or higher on an
Itanium machine. Using -O1 works.
On an x86 RedHat Linux machine the same test
case works with -O2 and above with gcc 3.2.
The Itanium optimizer appears to be producing
incorrect code.
>How-To-Repeat:
The following statement errors on an Itanium Linux machine.
The test case supplied being named Test.cc
# g++ -O2 Test.cc && a.out
>Fix:
Compile with -O1.
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: text/x-c++src; name="Test.cc"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="Test.cc"
I2luY2x1ZGUgPGlvc3RyZWFtPgoKLy8gY29tcGlsaW5nIHdpdGggLU8yIG9uIGFuIEl0YW5pdW0g
bWFjaGluZSAoZWcgIyBnKysgLU8yIFRlc3QuY2MgJiYgYS5vdXQpCi8vIHdpbGwgcHJvZHVjZSBh
biBpbGxlZ2FsIGluc3RydWN0aW9uIGVycm9yIChwbHVzIHRoZSB2YWx1ZXMgb2YgczIgYW5kCi8v
IHQyLnN0cmluZygpIHdpbGwgYmUgZGlmZmVyZW50KS4gVXNpbmcgLU8yIG9uIGFuIHg4NiBtYWNo
aW5lIHdvcmtzLiBMaWtld2lzZQovLyAtTzEgb24gYW4gSXRhbml1bSBtYWNoaW5lIGFsc28gd29y
a3MuCgpjbGFzcyBUZXN0CnsKcHVibGljOgoKICAgIFRlc3QoY29uc3QgY2hhciogcF9zdHIpIDog
c3RyKHBfc3RyKSB7fQogICAgY29uc3QgY2hhciogc3RyOwogICAgbG9uZyBsZW47Cn07CgoKaW50
Cm1haW4oY2hhcioqLCBpbnQpCnsKICAgIHsKICAgICAgICBUZXN0IHQoIkMiKTsKICAgIH0KICAg
IHsKICAgICAgICBjb25zdCBjaGFyIHNbXSA9ICJIZWxsbyB0aGVyZSI7CiAgICB9CiAgICB7CiAg
ICAgICAgY29uc3QgY2hhciBzW10gPSB7IDY3IH07CiAgICAgICAgVGVzdCB0KHMpOwoKICAgICAg
ICAvLyBPbiB0aGUgLU8yIEl0YW5pdW0gYnVpbGQgdGhlIGZvbGxvd2luZyB0d28gdmFsdWVzIGRp
ZmZlci4KICAgICAgICBzdGQ6OmNvdXQgPDwgInM6ICAgICAgICAgICAgICAiIDw8IChsb25nKXMg
PDwgc3RkOjplbmRsOwogICAgICAgIHN0ZDo6Y291dCA8PCAidC5zdHI6ICAgICAgICAgICIgPDwg
KGxvbmcpdC5zdHIgPDwgc3RkOjplbmRsOwoKICAgICAgICAvLyBQcmludCBvdXQgdGhlIGZpcnN0
IHZhbHVlLgogICAgICAgIHN0ZDo6Y291dCA8PCAic1swXTogICAgICAgICAgICIgPDwgc1swXSA8
PCBzdGQ6OmVuZGw7CgogICAgICAgIC8vIFdpdGggZysrIC1PMiB0aGlzIG5leHQgbGluZSBmYWxs
cyBvdmVyIG9uIGFuIEl0YW5pdW0uCiAgICAgICAgc3RkOjpjb3V0IDw8ICJ0LnN0clswXTogICAg
ICAgIiA8PCB0LnN0clswXSA8PCBzdGQ6OmVuZGw7CiAgICB9CgogICAgcmV0dXJuIDA7Cn0K
reply other threads:[~2002-09-04 3:16 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=20020904030929.20367.qmail@sources.redhat.com \
--to=dennis@mds.rmit.edu.au \
--cc=gcc-gnats@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).