public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/57600] Turn 2 comparisons into 1 with the min
Date: Thu, 13 Jun 2013 09:26:00 -0000	[thread overview]
Message-ID: <bug-57600-4-IoqbkYOUkP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57600-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57600

--- Comment #4 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #3)
> Perhaps we want to perform it just during ifcvt once it is rolled into
> vectorizer and works on an on-the-side bb?  Then it wouldn't affect
> non-vectorized code.

We would miss some useful cases (in the original testcase, the transformation
is worth it even without vectorizing), but at least it would make regressions
unlikely...


  parent reply	other threads:[~2013-06-13  9:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-12 18:48 [Bug tree-optimization/57600] New: " glisse at gcc dot gnu.org
2013-06-13  8:19 ` [Bug tree-optimization/57600] " rguenth at gcc dot gnu.org
2013-06-13  8:40 ` glisse at gcc dot gnu.org
2013-06-13  9:20 ` jakub at gcc dot gnu.org
2013-06-13  9:26 ` glisse at gcc dot gnu.org [this message]
2015-06-19 15:25 ` alalaw01 at gcc dot gnu.org
2015-06-19 16:20 ` glisse 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-57600-4-IoqbkYOUkP@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).