public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dannysmith at users dot sourceforge dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/35061] New: #pragma pop_macro causes ICE if no macro value on stack Date: Sun, 03 Feb 2008 08:40:00 -0000 [thread overview] Message-ID: <bug-35061-4066@http.gcc.gnu.org/bugzilla/> (raw) A "#pragma pop_macro" without a preceding "#pragma push_macro" triggers an ICE on mingw32 // pop_macro.c #define X 1 int main() { // # pragma push_macro("X") # undef X # define X 2 # pragma pop_macro("X") return 0; } gcc pop_macro.c pop_macro.c: In function 'main': pop_macro.c:9: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. -- Summary: #pragma pop_macro causes ICE if no macro value on stack Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: preprocessor AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: dannysmith at users dot sourceforge dot net GCC target triplet: i686-pc-mingw32 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35061
next reply other threads:[~2008-02-03 8:40 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-02-03 8:40 dannysmith at users dot sourceforge dot net [this message] 2008-02-06 10:57 ` [Bug preprocessor/35061] " fxcoudert at gcc dot gnu dot org 2008-02-06 17:30 ` dannysmith at users dot sourceforge dot net 2008-02-14 21:43 ` dannysmith at gcc dot gnu dot org 2008-02-14 21:45 ` dannysmith at users dot sourceforge dot net 2008-02-14 22:18 ` ubizjak at gmail dot com 2008-02-15 14:19 ` ubizjak at gmail dot com
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=bug-35061-4066@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).