public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: kendall@abinitio.com To: gcc-gnats@gcc.gnu.org Subject: c++/9211: Compiler segfault upon use of __noreturn__ function in static initializer Date: Tue, 07 Jan 2003 01:26:00 -0000 [thread overview] Message-ID: <20030107012415.2526.qmail@sources.redhat.com> (raw) >Number: 9211 >Category: c++ >Synopsis: Compiler segfault upon use of __noreturn__ function in static initializer >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Mon Jan 06 17:26:00 PST 2003 >Closed-Date: >Last-Modified: >Originator: kendall@abinitio.com >Release: 3.2.1 >Organization: >Environment: Red Hat Linux release 6.2 >Description: The code we found the bug looked like #include <assert.h> int dummy = (assert(blah), 0); See how-to-repeat for the preprocessed+simplified case. $ /usr/local/gcc/3.2.1/bin/gcc -v Reading specs from /usr/local/gcc/3.2.1/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/specs Configured with: ./configure --prefix=/usr/local/gcc/3.2.1 Thread model: posix gcc version 3.2.1 >How-To-Repeat: $ cat t.cpp int f() __attribute__ ((__noreturn__)); static int i = f(); $ /usr/local/gcc/3.2.1/bin/g++ -c t.cpp t.cpp:2: internal error: Segmentation fault [...] >Fix: >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2003-01-07 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=20030107012415.2526.qmail@sources.redhat.com \ --to=kendall@abinitio.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).