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/64454] optimize (x%5)%5
Date: Mon, 12 Jan 2015 20:52:00 -0000 [thread overview]
Message-ID: <bug-64454-4-Y35j0VkQHg@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
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2015-01-12
Ever confirmed|0 |1
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The reason for tree_int_cst_sgn (vr->min) >= 0 was that I don't want to let 0
through and for negative values, handling those would require computing
absolute value, but as match.pd already folds x % -5 already into x % 5, there
is no need to bother with it, so I'm just trying to play safe.
Anyway, keeping this open, as the (x%y)<y case is not handled yet.
next prev parent reply other threads:[~2015-01-12 20:52 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 [this message]
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
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-Y35j0VkQHg@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).