public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "d.g.gorbachev at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/54957] Two crashes introduced by rev192488 Date: Tue, 23 Oct 2012 21:16:00 -0000 [thread overview] Message-ID: <bug-54957-4-mSvBn8Grj1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54957-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54957 --- Comment #15 from Dmitry Gorbachev <d.g.gorbachev at gmail dot com> 2012-10-23 21:16:37 UTC --- Mingw32 target, GCC 4.8.0 20121021 (experimental). $ cat > bug.cc struct S { ~S(); }; int main() { S s1, s2, s3, s4, s5, s6, s7; return 0; } ^D $ g++ bug.cc bug.cc: In function 'int main()': bug.cc:9:1: internal compiler error: Segmentation fault } ^ 0x87e5f10 crash_signal ../../gcc-4.8/gcc/toplev.c:335 0x87d2428 emit_case_dispatch_table ../../gcc-4.8/gcc/stmt.c:1919 0x87d4ae5 expand_sjlj_dispatch_table(rtx_def*, vec_t<tree_node*>*) ../../gcc-4.8/gcc/stmt.c:2292 0x853e6cc sjlj_emit_dispatch_table ../../gcc-4.8/gcc/except.c:1363 0x853f900 sjlj_build_landing_pads ../../gcc-4.8/gcc/except.c:1420 0x853fa5b finish_eh_generation() ../../gcc-4.8/gcc/except.c:1454 0x8487921 gimple_expand_cfg ../../gcc-4.8/gcc/cfgexpand.c:4579 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <http://gcc.gnu.org/bugs.html> for instructions.
next prev parent reply other threads:[~2012-10-23 21:16 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-17 18:03 [Bug middle-end/54957] New: " rmansfield at qnx dot com 2012-10-17 18:04 ` [Bug middle-end/54957] " pinskia at gcc dot gnu.org 2012-10-17 18:05 ` rmansfield at qnx dot com 2012-10-17 18:08 ` eraman at google dot com 2012-10-17 18:10 ` rmansfield at qnx dot com 2012-10-17 18:25 ` eraman at google dot com 2012-10-17 18:26 ` eraman at google dot com 2012-10-17 18:30 ` rmansfield at qnx dot com 2012-10-17 18:56 ` eraman at google dot com 2012-10-17 19:05 ` rmansfield at qnx dot com 2012-10-17 19:47 ` rmansfield at qnx dot com 2012-10-17 20:31 ` eraman at google dot com 2012-10-17 20:39 ` rmansfield at qnx dot com 2012-10-22 23:37 ` amylaar at gcc dot gnu.org 2012-10-23 17:10 ` uweigand at gcc dot gnu.org 2012-10-23 21:16 ` d.g.gorbachev at gmail dot com [this message] 2012-10-27 15:15 ` mikpe at it dot uu.se 2012-10-28 16:38 ` amylaar at gcc dot gnu.org 2012-10-30 1:57 ` rbmj at verizon dot net 2012-10-30 1:59 ` rbmj at verizon dot net 2012-10-31 23:29 ` eraman at gcc dot gnu.org 2012-11-01 18:05 ` rbmj at verizon dot net 2013-12-17 16:03 ` ktietz at gcc dot gnu.org
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-54957-4-mSvBn8Grj1@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).