public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "belagod at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/63677] Failure to constant fold with vectorization.
Date: Wed, 29 Oct 2014 16:50:00 -0000 [thread overview]
Message-ID: <bug-63677-4-qLbdtL58HQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63677-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63677
--- Comment #1 from Tejas Belagod <belagod at gcc dot gnu.org> ---
There is similar behaviour on aarch64. So, it doesn't look like a backend
issue.
next parent reply other threads:[~2014-10-29 16:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-63677-4@http.gcc.gnu.org/bugzilla/>
2014-10-29 16:50 ` belagod at gcc dot gnu.org [this message]
2014-10-29 17:24 ` pinskia at gcc dot gnu.org
2014-10-29 18:21 ` jakub at gcc dot gnu.org
2014-10-30 9:52 ` rguenth at gcc dot gnu.org
2014-11-19 9:35 ` rguenth at gcc dot gnu.org
2014-11-20 8:41 ` rguenth at gcc dot gnu.org
2014-11-20 8:43 ` rguenth at gcc dot gnu.org
2014-11-20 12:44 ` 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-63677-4-qLbdtL58HQ@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: link
Be 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).