public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/50374] Support vectorization of min/max location pattern
Date: Wed, 21 Sep 2011 12:21:00 -0000 [thread overview]
Message-ID: <bug-50374-4-2dMTfjO8nC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50374-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50374
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #25320|0 |1
is obsolete| |
Attachment #25324|0 |1
is obsolete| |
Attachment #25325|0 |1
is obsolete| |
--- Comment #14 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-09-21 12:10:28 UTC ---
Created attachment 25331
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=25331
gcc47-pr50374.patch
Updated patch, not very heavily tested yet.
The optabs stuff needs to change, because currently i?86 has 480 gen_reduc*loc*
expanders, that's way too much.
Thus I think it will be better to only iterate on the two modes, and pass
the comparison operator as another argument like we pass to vcond{,u}, from
which the expansion can determine what kind of comparison is supposed to happen
(signed vs. unsigned, min vs. max and first vs. last). I'll change it now.
Another thing is that this really ought to work even with -ftree-pre, having a
vectorization that requires users to disable PRE would be weird. I believe
there is one extra assignment, will look at that.
Then there is the question if ifcvt should, as richi asked, fold the COND_EXPR
into MIN/MAX and vectorizer be adjusted for that. Or, if we just should it
vectorize it using two VECT_COND_EXPRs instead (with the same condition).
Then, can also vectorize e.g. double comparisons, but only int indexes?
next prev parent reply other threads:[~2011-09-21 12:10 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-13 7:55 [Bug tree-optimization/50374] New: " vincenzo.innocente at cern dot ch
2011-09-13 8:01 ` [Bug tree-optimization/50374] " irar at il dot ibm.com
2011-09-13 8:39 ` jakub at gcc dot gnu.org
2011-09-13 8:52 ` vincenzo.innocente at cern dot ch
2011-09-19 13:08 ` jakub at gcc dot gnu.org
2011-09-19 16:37 ` jakub at gcc dot gnu.org
2011-09-20 10:00 ` irar at il dot ibm.com
2011-09-20 12:05 ` irar at il dot ibm.com
2011-09-20 12:18 ` irar at il dot ibm.com
2011-09-20 12:20 ` vincenzo.innocente at cern dot ch
2011-09-20 12:28 ` irar at il dot ibm.com
2011-09-20 12:30 ` irar at il dot ibm.com
2011-09-20 14:00 ` vincenzo.innocente at cern dot ch
2011-09-20 14:57 ` jakub at gcc dot gnu.org
2011-09-21 12:21 ` jakub at gcc dot gnu.org [this message]
2011-09-21 12:51 ` irar at il dot ibm.com
2011-09-21 16:58 ` jakub at gcc dot gnu.org
2011-09-21 17:37 ` jakub at gcc dot gnu.org
2011-09-22 8:51 ` irar at il dot ibm.com
2011-09-22 15:32 ` jakub at gcc dot gnu.org
2011-09-22 16:27 ` jakub at gcc dot gnu.org
2011-11-29 9:59 ` vincenzo.innocente at cern dot ch
2011-11-29 10:03 ` jakub at gcc dot gnu.org
2011-11-29 10:27 ` vincenzo.innocente at cern dot ch
2011-11-29 15:27 ` jakub at gcc dot gnu.org
2011-11-29 15:54 ` vincenzo.innocente at cern dot ch
2011-11-30 10:52 ` vincenzo.innocente at cern dot ch
2014-08-23 17:37 ` vincenzo.innocente at cern dot ch
2014-08-24 10:30 ` Joost.VandeVondele at mat dot ethz.ch
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-50374-4-2dMTfjO8nC@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).