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 tree-optimization/66396] [6 regression] FAIL: gcc.dg/graphite/run-id-pr47593.c execution test Date: Mon, 08 Jun 2015 11:51:00 -0000 [thread overview] Message-ID: <bug-66396-4-ydoAQYbAsc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66396-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66396 --- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> --- The issue is corrupted VOPs. <bb 2>: # .MEM_4 = VDEF <.MEM_3(D)> iD.1808@ = 1; # .MEM_5 = VDEF <.MEM_4> xD.1810@ = &iD.1808@; # .MEM_6 = VDEF <.MEM_5> yD.1811@ = &jD.1807@; # .MEM_7 = VDEF <.MEM_6> fD.1806@.pD.1801 = &yD.1811@; # .MEM_8 = VDEF <.MEM_7> fD.1806@.qD.1802 = &xD.1810@; # PT = { D.1806 } p_25 = &fD.1806@ + 4; # .MEM_28 = VDEF <.MEM_3(D)> jD.1807@ = 4; see how that uses the wrong VUSE.
next prev parent reply other threads:[~2015-06-08 11:51 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-03 11:27 [Bug tree-optimization/66396] New: " schwab@linux-m68k.org 2015-06-03 11:29 ` [Bug tree-optimization/66396] " schwab@linux-m68k.org 2015-06-03 12:11 ` rguenth at gcc dot gnu.org 2015-06-03 13:04 ` rguenth at gcc dot gnu.org 2015-06-04 4:13 ` amker at gcc dot gnu.org 2015-06-04 4:13 ` amker at gcc dot gnu.org 2015-06-04 11:15 ` rguenth at gcc dot gnu.org 2015-06-08 11:51 ` rguenth at gcc dot gnu.org [this message] 2015-06-08 12:18 ` rguenth at gcc dot gnu.org 2015-06-09 7:52 ` rguenth at gcc dot gnu.org 2015-06-09 8:22 ` rguenth 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-66396-4-ydoAQYbAsc@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).