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/59100] requesting optimization of safe rotate function
Date: Thu, 08 May 2014 13:17:00 -0000	[thread overview]
Message-ID: <bug-59100-4-z9UhsFqJeE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59100-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Marc Glisse <glisse at gcc dot gnu.org> ---
Author: glisse
Date: Thu May  8 13:17:01 2014
New Revision: 210212

URL: http://gcc.gnu.org/viewcvs?rev=210212&root=gcc&view=rev
Log:
2014-05-08  Marc Glisse  <marc.glisse@inria.fr>

    PR tree-optimization/59100
gcc/
    * tree-ssa-phiopt.c: Include tree-inline.h.
    (neutral_element_p, absorbing_element_p): New functions.
    (value_replacement): Handle conditional binary operations with a
    neutral or absorbing element.
gcc/testsuite/
    * gcc.dg/tree-ssa/phi-opt-12.c: New file.
    * gcc.dg/tree-ssa/phi-opt-13.c: Likewise.

Added:
    trunk/gcc/testsuite/gcc.dg/tree-ssa/phi-opt-12.c
    trunk/gcc/testsuite/gcc.dg/tree-ssa/phi-opt-13.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/tree-ssa-phiopt.c


  parent reply	other threads:[~2014-05-08 13:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-59100-4@http.gcc.gnu.org/bugzilla/>
2013-11-13  7:03 ` [Bug c/59100] " glisse at gcc dot gnu.org
2013-11-13  8:06 ` jakub at gcc dot gnu.org
2013-11-13 12:20 ` [Bug tree-optimization/59100] " rguenth at gcc dot gnu.org
2014-02-01 18:42 ` glisse at gcc dot gnu.org
2014-05-08 13:17 ` glisse at gcc dot gnu.org [this message]
2014-05-08 13:23 ` 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-59100-4-z9UhsFqJeE@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).