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/64454] optimize (x%5)%5
Date: Sat, 09 May 2015 15:40:00 -0000	[thread overview]
Message-ID: <bug-64454-4-xH8xt1h2YD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64454-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from Marc Glisse <glisse at gcc dot gnu.org> ---
Author: glisse
Date: Sat May  9 15:40:05 2015
New Revision: 222970

URL: https://gcc.gnu.org/viewcvs?rev=222970&root=gcc&view=rev
Log:
2015-05-09  Marc Glisse  <marc.glisse@inria.fr>

        PR tree-optimization/64454
gcc/
        * tree-vrp.c (extract_range_from_binary_expr_1) <TRUNC_MOD_EXPR>:
        Rewrite.
gcc/testsuite/
        * gcc.dg/tree-ssa/vrp97.c: New file.
        * gcc.dg/vect/slp-perm-7.c: Update.

Added:
    trunk/gcc/testsuite/gcc.dg/tree-ssa/vrp97.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/testsuite/gcc.dg/vect/slp-perm-7.c
    trunk/gcc/tree-vrp.c


  parent reply	other threads:[~2015-05-09 15:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-31 12:25 [Bug tree-optimization/64454] New: " glisse at gcc dot gnu.org
2015-01-02 20:35 ` [Bug tree-optimization/64454] " glisse at gcc dot gnu.org
2015-01-12 17:54 ` jakub at gcc dot gnu.org
2015-01-12 19:53 ` glisse at gcc dot gnu.org
2015-01-12 20:45 ` jakub at gcc dot gnu.org
2015-01-12 20:52 ` jakub at gcc dot gnu.org
2015-01-12 21:16 ` jakub at gcc dot gnu.org
2015-05-01 10:21 ` glisse at gcc dot gnu.org
2015-05-09 15:40 ` glisse at gcc dot gnu.org [this message]
2015-05-15 17:40 ` glisse at gcc dot gnu.org
2015-05-15 18:07 ` pinskia at gcc dot gnu.org
2015-05-15 18:30 ` glisse at gcc dot gnu.org
2022-02-24 10:33 ` pinskia 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-64454-4-xH8xt1h2YD@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).