public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/66726] missed optimization, factor conversion out of COND_EXPR
Date: Fri, 03 Jul 2015 12:21:00 -0000	[thread overview]
Message-ID: <bug-66726-4-KlDqEeHUeY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66726-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66726

--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to kugan from comment #3)
> > really you should handle more
> > than two arguments to phis.
> I am not sure how we can handle phi stmt with more than two arguments here.
> Any hints please?

Yes they are all interger constants but one of them. Also I think you do have
another bug where the conversion is an extension the original interger has to
fit in the new type. That is if you converting from char to int.


  parent reply	other threads:[~2015-07-03 12:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-01 17:23 [Bug tree-optimization/66726] New: " law at redhat dot com
2015-07-02  6:21 ` [Bug tree-optimization/66726] " kugan at gcc dot gnu.org
2015-07-02  6:25 ` pinskia at gcc dot gnu.org
2015-07-03 12:12 ` kugan at gcc dot gnu.org
2015-07-03 12:21 ` pinskia at gcc dot gnu.org [this message]
2015-07-03 12:25 ` kugan at gcc dot gnu.org
2015-07-06 20:40 ` law at redhat dot com
2015-07-06 20:56 ` law at redhat dot com
2015-07-13  9:47 ` schwab@linux-m68k.org
2015-07-13 21:34 ` law at redhat dot com
2015-07-13 23:39 ` kugan at gcc dot gnu.org
2015-07-14 13:20 ` kugan 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-66726-4-KlDqEeHUeY@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).