public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/59594] [4.9 Regression] wrong code (by tree vectorizer) at -O3 on x86_64-linux-gnu Date: Tue, 24 Dec 2013 18:37:00 -0000 [thread overview] Message-ID: <bug-59594-4-eFamFOuB7i@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59594-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59594 H.J. Lu <hjl.tools at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rguenther at suse dot de --- Comment #1 from H.J. Lu <hjl.tools at gmail dot com> --- It is caused by r204062.
next prev parent reply other threads:[~2013-12-24 18:37 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-12-24 17:14 [Bug tree-optimization/59594] New: " su at cs dot ucdavis.edu 2013-12-24 18:10 ` [Bug tree-optimization/59594] [4.9 Regression] " hjl.tools at gmail dot com 2013-12-24 18:37 ` hjl.tools at gmail dot com [this message] 2014-01-13 10:19 ` jakub at gcc dot gnu.org 2014-01-13 13:47 ` hjl.tools at gmail dot com 2014-01-13 14:02 ` jakub at gcc dot gnu.org 2014-01-22 13:22 ` jakub at gcc dot gnu.org 2014-01-24 10:03 ` jakub at gcc dot gnu.org 2014-01-29 9:28 ` jakub at gcc dot gnu.org 2014-01-29 11:04 ` jakub 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-59594-4-eFamFOuB7i@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).