public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/57661] New: [4.9 Regression] ICE: SIGSEGV in verify_ssa
Date: Thu, 20 Jun 2013 13:37:00 -0000	[thread overview]
Message-ID: <bug-57661-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57661

            Bug ID: 57661
           Summary: [4.9 Regression] ICE: SIGSEGV in verify_ssa
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
          Assignee: unassigned at gcc dot gnu.org
          Reporter: zsojka at seznam dot cz

Created attachment 30326
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30326&action=edit
partially reduced testcase

Compiler output:
$ gcc -O2 -fno-tree-forwprop -std=gnu++0x testcase.C
testcase.C: In destructor '_Rope_RopeFunction<_CharT,
_Alloc>::~_Rope_RopeFunction() [with _CharT = char; _Alloc = allocator<char>]':
testcase.C:54:5: internal compiler error: Segmentation fault
     ~_Rope_RopeFunction () throw ()
     ^
0xbe9c8f crash_signal
        /mnt/svn/gcc-trunk/gcc/toplev.c:333
0xd6b5f0 verify_ssa(bool)
        /mnt/svn/gcc-trunk/gcc/tree-ssa.c:938
0xafc281 execute_function_todo
        /mnt/svn/gcc-trunk/gcc/passes.c:1970
0xafcbe7 execute_todo
        /mnt/svn/gcc-trunk/gcc/passes.c:2002
0xafe8e1 execute_one_ipa_transform_pass
        /mnt/svn/gcc-trunk/gcc/passes.c:2185
0xafe8e1 execute_all_ipa_transforms()
        /mnt/svn/gcc-trunk/gcc/passes.c:2215
0x874a38 expand_function
        /mnt/svn/gcc-trunk/gcc/cgraphunit.c:1584
0x8766f6 expand_all_functions
        /mnt/svn/gcc-trunk/gcc/cgraphunit.c:1695
0x8766f6 compile()
        /mnt/svn/gcc-trunk/gcc/cgraphunit.c:2029
0x876cc9 finalize_compilation_unit()
        /mnt/svn/gcc-trunk/gcc/cgraphunit.c:2106
0x685d60 cp_write_global_declarations()
        /mnt/svn/gcc-trunk/gcc/cp/decl2.c:4356
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.


$ gcc -v                                            
Using built-in specs.
COLLECT_GCC=/mnt/svn/gcc-trunk/binary-latest/bin/gcc
COLLECT_LTO_WRAPPER=/mnt/svn/gcc-trunk/binary-200224-lto-fortran-checking-yes-rtl-df/libexec/gcc/x86_64-unknown-linux-gnu/4.9.0/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: /mnt/svn/gcc-trunk//configure --enable-checking=yes,rtl,df
--enable-languages=c,c++,lto,fortran
--prefix=/mnt/svn/gcc-trunk/binary-200224-lto-fortran-checking-yes-rtl-df/
--without-cloog --without-ppl
Thread model: posix
gcc version 4.9.0 20130619 (experimental) (GCC) 

Tested revisions:
r200224 - crash
4.8 r198018 - OK


             reply	other threads:[~2013-06-20 13:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-20 13:37 zsojka at seznam dot cz [this message]
2013-06-24 11:09 ` [Bug middle-end/57661] " rguenth at gcc dot gnu.org
2013-07-12  1:50 ` mpolacek at gcc dot gnu.org
2013-07-22 22:03 ` jakub at gcc dot gnu.org
2013-07-22 22:36 ` jakub at gcc dot gnu.org
2013-07-22 23:50 ` jakub at gcc dot gnu.org
2013-08-13 19:58 ` jakub 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-57661-4@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: 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).