public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: nick@ilm.com
To: gcc-gnats@gcc.gnu.org
Subject: c++/9786: g++ ice on x86 with -fnon-call-exceptions and -O2
Date: Fri, 21 Feb 2003 01:26:00 -0000 [thread overview]
Message-ID: <20030221012542.30285.qmail@sources.redhat.com> (raw)
>Number: 9786
>Category: c++
>Synopsis: g++ ice on x86 with -fnon-call-exceptions and -O2
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: ice-on-legal-code
>Submitter-Id: net
>Arrival-Date: Fri Feb 21 01:26:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: nick@ilm.com
>Release: gcc-3.2.2, gcc version 3.3 20030220 (prerelease)
>Organization:
>Environment:
x86 redhat-7.2 with current updates
>Description:
the same ICE occurs with both gcc-3.2.2 and the head
of the gcc-3_3-branch:
> /dept/rnd/vendor/gcc-3.3cvs/bin/g++ -v -fnon-call-exceptions -Wall -O2 -c foo.C -o foo.o
Reading specs from /dept/rnd/vendor/gcc-3.3cvs/lib/gcc-lib/i686-pc-linux-gnu/3.3/specs
Configured with: ../gcc/configure --prefix=/dept/rnd/vendor/gcc-3.3cvs --enable-threads --enable-languages=c,c++
Thread model: posix
gcc version 3.3 20030220 (prerelease)
/dept/rnd/vendor/gcc-3.3cvs/lib/gcc-lib/i686-pc-linux-gnu/3.3/cc1plus -quiet -v -D__GNUC__=3 -D__GNUC_MINOR__=3 -D__GNUC_PATCHLEVEL__=0 -D_GNU_SOURCE foo
.C -D__GNUG__=3 -quiet -dumpbase foo.C -auxbase-strip foo.o -O2 -Wall -version -fnon-call-exceptions -o /usr/tmp/ccNboRkg.s
GNU C++ version 3.3 20030220 (prerelease) (i686-pc-linux-gnu)
compiled by GNU C version 2.96 20000731 (Red Hat Linux 7.1 2.96-98).
ignoring nonexistent directory "/dept/rnd/vendor/gcc-3.3cvs/i686-pc-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
/dept/rnd/vendor/gcc-3.3cvs/include/c++/3.3
/dept/rnd/vendor/gcc-3.3cvs/include/c++/3.3/i686-pc-linux-gnu
/dept/rnd/vendor/gcc-3.3cvs/include/c++/3.3/backward
/usr/local/include
/dept/rnd/vendor/gcc-3.3cvs/include
/dept/rnd/vendor/gcc-3.3cvs/lib/gcc-lib/i686-pc-linux-gnu/3.3/include
/usr/include
End of search list.
foo.C: In constructor `B::B(const D2&)':
foo.C:20: internal compiler error: in fixup_abnormal_edges, at reload1.c:9498
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
A small test case demonstrating this is attached.
This bug may be related to the previously reported
fixup_abnormal_edges optimization bugs triggered
with gcj compiles - 6581 and 4571.
>How-To-Repeat:
g++ -fnon-call-exceptions -Wall -O2 -c foo.C -o foo.o
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="foo.C"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="foo.C"
c3RydWN0IEQxIHsKICAgIGZsb2F0IGw7CiAgICBEMSBHUygpIGNvbnN0IHtEMSBkO2Zsb2F0IGY9
LjI5OSpsO2QubD1mO3JldHVybiBkO30KICAgIHN0YXRpYyBEMSBHKCkge3JldHVybiBEMSgpO30K
fTsKc3RydWN0IEQyIHsKICAgIEQxIGc7CiAgICBEMihjb25zdCBEMSYgZ2kpIDogZyhnaSkge30K
ICAgIEQyIEdTKCkgY29uc3Qge3JldHVybiBEMihnLkdTKCkpO30KfTsKY2xhc3MgQSB7CiAgcHVi
bGljOgogICAgdmlydHVhbCB+QSgpIHt9Cn07CmNsYXNzIEIgOiBwdWJsaWMgQSB7CiAgcHVibGlj
OgogICAgQihjb25zdCBEMiYgbWkpOwogICAgRDIgZm07Cn07CkI6OkIoY29uc3QgRDIgJm1pKSA6
IGZtKG1pLkdTKCkpIHt9Cg==
reply other threads:[~2003-02-21 1:26 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=20030221012542.30285.qmail@sources.redhat.com \
--to=nick@ilm.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: 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).