public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/67323] Use non-unit stride loads by preference when applicable Date: Tue, 25 Aug 2015 10:05:00 -0000 [thread overview] Message-ID: <bug-67323-4-yohcaNNPnK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67323-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67323 --- Comment #3 from rguenther at suse dot de <rguenther at suse dot de> --- On Tue, 25 Aug 2015, michael.collison at linaro dot org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67323 > > --- Comment #2 from Michael Collison <michael.collison at linaro dot org> --- > Richard, > > Should I create a test case that fails until you resolve this in GCC 6? If you can provide one that I can check in together with a fix that would be nice. Having it in the tree now and FAILing isn't according to our policies. > On 08/25/2015 02:14 AM, rguenth at gcc dot gnu.org wrote: > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67323 > > > > Richard Biener <rguenth at gcc dot gnu.org> changed: > > > > What |Removed |Added > > ---------------------------------------------------------------------------- > > Status|UNCONFIRMED |ASSIGNED > > Last reconfirmed| |2015-08-25 > > CC|richard.guenther at gmail dot com |rguenth at gcc dot gnu.org > > Depends on| |66721 > > Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org > > Ever confirmed|0 |1 > > > > --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- > > Confirmed. We go down the SLP path here because the vectorizer thinks that > > SLP is always cheaper than using interleaving (which generally is true > > if there were not targets which can do the load plus interleave with > > load-lanes ...). > > > > I think this may be a regression as well because I enhanced SLP to apply > > to way more cases. > > > > Note that my plan is to make the vectorizer consider both (well, not really, > > but this bug shows I maybe should try), SLP and non-SLP, and evaluate based > > on costs which route to go. > > > > > > Referenced Bugs: > > > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66721 > > [Bug 66721] [6 regression] gcc.target/i386/pr61403.c FAILs > >
next prev parent reply other threads:[~2015-08-25 10:05 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-08-23 3:14 [Bug tree-optimization/67323] New: " michael.collison at linaro dot org 2015-08-25 9:14 ` [Bug tree-optimization/67323] " rguenth at gcc dot gnu.org 2015-08-25 9:57 ` michael.collison at linaro dot org 2015-08-25 10:05 ` rguenther at suse dot de [this message] 2015-08-25 10:14 ` michael.collison at linaro dot org 2015-10-07 11:37 ` rguenth at gcc dot gnu.org 2021-05-04 12:32 ` 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-67323-4-yohcaNNPnK@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).