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 sanitizer/56330] New: [4.8 Regression] ICE: verify_gimple failed: gimple_bb (stmt) is set to a wrong basic block with -fsanitize=address
Date: Thu, 14 Feb 2013 21:51:00 -0000	[thread overview]
Message-ID: <bug-56330-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 56330
           Summary: [4.8 Regression] ICE: verify_gimple failed: gimple_bb
                    (stmt) is set to a wrong basic block with
                    -fsanitize=address
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: sanitizer
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: zsojka@seznam.cz
                CC: dodji@gcc.gnu.org, dvyukov@gcc.gnu.org,
                    jakub@gcc.gnu.org, kcc@gcc.gnu.org


Created attachment 29456
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29456
autoreduced testcase

I am not sure if this should be marked as a regression - the code doesn't
compile in 4.7, but used to older revisions of 4.8.

Compiler output:
$ gcc -fsanitize=address testcase.c         
testcase.c: In function 'foo':
testcase.c:10:1: error: gimple_bb (stmt) is set to a wrong basic block
 foo (void)
 ^
__builtin_memcmp (&s.a, &empty, 200);

testcase.c:10:1: error: gimple_bb (stmt) is set to a wrong basic block
return;

testcase.c:10:1: internal compiler error: verify_gimple failed
0xa528bc verify_gimple_in_cfg(function*)
        /mnt/svn/gcc-trunk/gcc/tree-cfg.c:4727
0x93f177 execute_function_todo
        /mnt/svn/gcc-trunk/gcc/passes.c:1970
0x93fa97 execute_todo
        /mnt/svn/gcc-trunk/gcc/passes.c:1999
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.

Tested revisions:
r196044 - crash
r195931 - OK


             reply	other threads:[~2013-02-14 21:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-14 21:51 zsojka at seznam dot cz [this message]
2013-02-14 22:03 ` [Bug sanitizer/56330] " mpolacek at gcc dot gnu.org
2013-02-14 22:23 ` [Bug sanitizer/56330] " steven at gcc dot gnu.org
2013-02-14 22:34 ` jakub at gcc dot gnu.org
2013-02-15  9:09 ` jakub at gcc dot gnu.org
2013-02-15 10:59 ` dodji at gcc dot gnu.org
2013-02-15 19:47 ` dodji at gcc dot gnu.org
2013-02-15 19:57 ` jakub at gcc dot gnu.org
2013-02-16  9:30 ` dodji at gcc dot gnu.org
2013-02-16  9:33 ` dodji at gcc dot gnu.org
2013-02-16  9:58 ` dodji 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-56330-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).