public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dodji at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/56330] ICE: verify_gimple failed: gimple_bb (stmt) is set to a wrong basic block with -fsanitize=address Date: Fri, 15 Feb 2013 19:47:00 -0000 [thread overview] Message-ID: <bug-56330-4-tCqZvflDta@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56330-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56330 --- Comment #5 from Dodji Seketeli <dodji at gcc dot gnu.org> 2013-02-15 19:46:44 UTC --- Created attachment 29477 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29477 Updated patch with cleanups explained in the ChangeLog Thanks! I have updated the patch to simplify the logic in instrument_mem_region_access somewhat, especially the part that does the statement iterator decrementing dance. I have also added more regression tests. What do you think?
next prev parent reply other threads:[~2013-02-15 19:47 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-02-14 21:51 [Bug sanitizer/56330] New: [4.8 Regression] " zsojka at seznam dot cz 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 [this message] 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-tCqZvflDta@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).