public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: gawrilow@math.tu-berlin.de To: gcc-gnats@gcc.gnu.org Subject: c++/6723: ICE on source code successfully compiled by previous versions Date: Sun, 19 May 2002 14:16:00 -0000 [thread overview] Message-ID: <20020519210802.8117.qmail@sources.redhat.com> (raw) >Number: 6723 >Category: c++ >Synopsis: ICE on source code successfully compiled by previous versions >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: ice-on-legal-code >Submitter-Id: net >Arrival-Date: Sun May 19 14:16:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Ewgenij Gawrilow >Release: 3.1 >Organization: >Environment: RedHat Linux 7.2 on an AMD Athlon PC $ g++ -v Reading specs from /usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.1/specs Configured with: ../gcc-3.1/configure --enable-shared --enable-threads=posix --with-gxx-include-dir=/usr/local/include/C++ --enable-languages=c++,java --with-cpu=athlon --enable-libgcj --disable-nls --with-system-zlib Thread model: posix gcc version 3.1 >Description: The attached code snippet was successfully compiled by gcc 3.0.2 .. 3.0.4, but now causes 3.1 to crash with segmentation fault. >How-To-Repeat: Just try to compile the code. Although extremely short, it suffices to trigger the bug. >Fix: >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/octet-stream; name="crash.cc" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="crash.cc" dGVtcGxhdGUgPHR5cGVuYW1lIEEsIHR5cGVuYW1lIEIsIHRlbXBsYXRlIDx0eXBlbmFtZSx0eXBl bmFtZT4gY2xhc3MgUHJlZGljYXRlLAogICAgICAgICAgYm9vbCBfbWF0Y2hlcz1QcmVkaWNhdGU8 QSxCPjo6YW5zd2VyPgpzdHJ1Y3QgaGVscGVyIHsgfTsK
next reply other threads:[~2002-05-19 21:16 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-05-19 14:16 gawrilow [this message] 2002-05-22 7:10 lerdsuwa 2002-05-24 7:52 lerdsuwa 2002-06-20 8:19 lerdsuwa
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=20020519210802.8117.qmail@sources.redhat.com \ --to=gawrilow@math.tu-berlin.de \ --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).