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 target/56865] [4.9 regression] FAIL: gcc.dg/vect/vect-42.c scan-tree-dump-times vect "Vectorizing an unaligned access" 4 Date: Fri, 25 Oct 2013 13:21:00 -0000 [thread overview] Message-ID: <bug-56865-4-TUA9hQyzPE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56865-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56865 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> --- Doesn't fail anymore according to http://gcc.gnu.org/ml/gcc-testresults/2013-10/msg01946.html
next prev parent reply other threads:[~2013-10-25 13:21 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-07 14:57 [Bug target/56865] New: " schwab@linux-m68k.org 2013-04-07 15:09 ` [Bug target/56865] " dominiq at lps dot ens.fr 2013-04-08 11:16 ` rguenth at gcc dot gnu.org 2013-05-01 21:58 ` wschmidt at gcc dot gnu.org 2013-05-02 7:38 ` rguenther at suse dot de 2013-05-02 15:27 ` wschmidt at gcc dot gnu.org 2013-05-02 15:29 ` wschmidt at gcc dot gnu.org 2013-05-02 15:29 ` wschmidt at gcc dot gnu.org 2013-10-25 12:53 ` rguenth at gcc dot gnu.org 2013-10-25 13:21 ` rguenth at gcc dot gnu.org [this message] 2013-10-28 2:11 ` wschmidt at gcc dot gnu.org 2013-10-29 13:15 ` [Bug target/56865] [4.9 regression] FAIL: gcc.dg/vect/vect-96.c scan-tree-dump-times vect "Alignment of access forced using peeling" 1 rguenth at gcc dot gnu.org 2013-10-29 13:17 ` rguenth at gcc dot gnu.org 2013-10-29 14:02 ` wschmidt at gcc dot gnu.org 2013-10-29 14:14 ` rguenther at suse dot de 2013-10-29 14:35 ` rguenth at gcc dot gnu.org 2013-10-29 17:44 ` wschmidt at gcc dot gnu.org 2013-10-30 9:55 ` rguenth at gcc dot gnu.org 2013-10-30 14:24 ` wschmidt at gcc dot gnu.org 2013-10-30 15:03 ` wschmidt at gcc dot gnu.org 2013-10-30 15:05 ` wschmidt at gcc dot gnu.org 2014-02-03 9:47 ` rguenth at gcc dot gnu.org 2014-02-03 15:05 ` wschmidt at gcc dot gnu.org 2014-02-03 15:09 ` rguenther at suse dot de 2014-02-03 15:13 ` jakub at gcc dot gnu.org 2014-02-03 15:32 ` wschmidt at gcc dot gnu.org 2014-02-03 16:48 ` wschmidt 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-56865-4-TUA9hQyzPE@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).