public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: janis187@us.ibm.com To: gcc-gnats@gcc.gnu.org Subject: target/6043: IICE on ia64 for Blitz config test for C++ complex math Date: Fri, 22 Mar 2002 17:36:00 -0000 [thread overview] Message-ID: <20020323013134.14401.qmail@sources.redhat.com> (raw) >Number: 6043 >Category: target >Synopsis: IICE on ia64 for Blitz config test for C++ complex math >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: ice-on-legal-code >Submitter-Id: net >Arrival-Date: Fri Mar 22 17:36:00 PST 2002 >Closed-Date: >Last-Modified: >Originator: Janis Johnson >Release: gcc version 3.1 20020321 (prerelease) >Organization: >Environment: Itanium, Red Hat Linux release 7.2 (Enigma) >Description: The GCC 3.1 prerelease and GCC 3.0.4 C++ compilers ICE on ia64-unknown-linux-gnu when compiling a configuration test for Blitz that checks for support of complex math: compmath.cpp: In function `int main()': compmath.cpp:18: Internal compiler error in change_address_1, at emit-rtl.c: 1910 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. I'm attaching the unpreprocessed file since it only includes <complex> and the preprocessed file is huge. I'm sure someone will let me know if they want the whole thing. >How-To-Repeat: Compile compmath.cpp with default options. >Fix: Unknown. >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/octet-stream; name="compmath.cpp" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="compmath.cpp" Ly8gQlpfSEFWRV9DT01QTEVYX01BVEgxCi8vIENvbXBsZXggbWF0aCBmdW5jdGlvbnMsIGFzIHBl ciAyNi4yLjcgb2YgdGhlIEphbic5NiBkcmFmdCBzdGFuZGFyZAojaW5jbHVkZSA8Y29tcGxleD4K CiNpZm5kZWYgQlpfTk9fTkFNRVNQQUNFUwp1c2luZyBuYW1lc3BhY2Ugc3RkOwojZW5kaWYKCmlu dCBtYWluKCkKewogICAgY29tcGxleDxkb3VibGU+IHgoMS4wLCAxLjApLCB5KDEuMCwgMS4wKTsK CiAgICByZWFsKHgpOwogICAgaW1hZyh4KTsKICAgIGFicyh4KTsKICAgIGFyZyh4KTsKICAgIG5v cm0oeCk7CiAgICBjb25qKHgpOwogICAgcG9sYXIoMS4wLDEuMCk7CgogICAgY29zKHgpOwogICAg Y29zaCh4KTsKICAgIGV4cCh4KTsKICAgIGxvZyh4KTsKICAgIGxvZzEwKHgpOwogICAgcG93KHgs MSk7ICAgCiAgICBwb3coeCxkb3VibGUoMi4wKSk7CiAgICBwb3coeCwgeSk7CiAgICBwb3coZG91 YmxlKDIuMCksIHgpOwogICAgc2luKHgpOwogICAgc2luaCh4KTsKICAgIHNxcnQoeCk7CiAgICB0 YW4oeCk7CiAgICB0YW5oKHgpOwoKICAgIHJldHVybiAwOwp9Cgo=
next reply other threads:[~2002-03-23 1:36 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-22 17:36 janis187 [this message] 2002-03-23 3:51 jakub 2002-03-25 4:25 jakub
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=20020323013134.14401.qmail@sources.redhat.com \ --to=janis187@us.ibm.com \ --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: linkBe 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).