public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/94913] Failure to optimize not+cmp into overflow check
Date: Fri, 08 May 2020 07:33:09 +0000 [thread overview]
Message-ID: <bug-94913-4-9EU7pIVc45@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94913-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94913
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:ff33680165346cb291667f38dd2e9f25a74cc3c3
commit r11-193-gff33680165346cb291667f38dd2e9f25a74cc3c3
Author: Jakub Jelinek <jakub@redhat.com>
Date: Fri May 8 09:32:20 2020 +0200
match.pd: Simplify unsigned A - B - 1 >= A to B >= A [PR94913]
Implemented thusly. The TYPE_OVERFLOW_WRAPS is there just because the
pattern above it has it too, if you want, I can throw it away from both.
2020-05-08 Jakub Jelinek <jakub@redhat.com>
PR tree-optimization/94913
* match.pd (A - B + -1 >= A to B >= A): New simplification.
(A - B > A to A < B): Don't test TYPE_OVERFLOW_WRAPS which is
always
true for TYPE_UNSIGNED integral types.
* gcc.dg/tree-ssa/pr94913.c: New test.
next prev parent reply other threads:[~2020-05-08 7:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-02 2:15 [Bug tree-optimization/94913] New: " gabravier at gmail dot com
2020-05-02 2:18 ` [Bug tree-optimization/94913] " gabravier at gmail dot com
2020-05-05 20:03 ` ubizjak at gmail dot com
2020-05-05 20:06 ` ubizjak at gmail dot com
2020-05-06 13:23 ` jakub at gcc dot gnu.org
2020-05-06 15:35 ` cvs-commit at gcc dot gnu.org
2020-05-08 7:33 ` cvs-commit at gcc dot gnu.org [this message]
2020-05-08 7:51 ` jakub 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-94913-4-9EU7pIVc45@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).