public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/66314] [6 Regression] ice in verify_loop_structure Date: Mon, 01 Jun 2015 13:55:00 -0000 [thread overview] Message-ID: <bug-66314-4-b6vJlV6jan@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66314-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66314 --- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> --- Author: rguenth Date: Mon Jun 1 13:55:12 2015 New Revision: 223979 URL: https://gcc.gnu.org/viewcvs?rev=223979&root=gcc&view=rev Log: 2015-06-01 Richard Biener <rguenther@suse.de> Revert 2015-05-29 Richard Biener <rguenther@suse.de> PR tree-optimization/66314 * tree-ssa-threadupdate.c (create_block_for_threading): Add parameter that says which loop the new block belongs to. (ssa_create_duplicates): Blocks duplicated for the threaded path belong to the loop of the thread destination. * gcc.dg/asan/pr66314.c: New testcase. Removed: trunk/gcc/testsuite/gcc.dg/asan/pr66314.c Modified: trunk/gcc/ChangeLog trunk/gcc/testsuite/ChangeLog trunk/gcc/tree-ssa-threadupdate.c
next prev parent reply other threads:[~2015-06-01 13:55 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-05-27 19:15 [Bug c/66314] New: " dcb314 at hotmail dot com 2015-05-28 7:34 ` [Bug middle-end/66314] " rguenth at gcc dot gnu.org 2015-05-28 7:56 ` [Bug middle-end/66314] [6 Regression] " rguenth at gcc dot gnu.org 2015-05-28 14:44 ` rguenth at gcc dot gnu.org 2015-05-28 14:50 ` ktkachov at gcc dot gnu.org 2015-05-28 15:24 ` jakub at gcc dot gnu.org 2015-05-28 15:25 ` jakub at gcc dot gnu.org 2015-05-29 10:51 ` rguenth at gcc dot gnu.org 2015-05-29 11:07 ` rguenth at gcc dot gnu.org 2015-06-01 13:55 ` rguenth at gcc dot gnu.org [this message] 2015-06-01 13:58 ` rguenth at gcc dot gnu.org 2015-06-01 14:00 ` rguenth at gcc dot gnu.org 2015-07-21 8:11 ` trippels at gcc dot gnu.org 2015-08-03 16:27 ` law at redhat 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-66314-4-b6vJlV6jan@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).