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/94921] Failure to optimize nots with sub into single add
Date: Wed, 06 May 2020 09:20:51 +0000 [thread overview]
Message-ID: <bug-94921-4-euUUosVv8f@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94921-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94921
--- Comment #4 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:a7b76d574b19190da190a60c065f347f40bab59e
commit r11-132-ga7b76d574b19190da190a60c065f347f40bab59e
Author: Jakub Jelinek <jakub@redhat.com>
Date: Wed May 6 11:20:20 2020 +0200
match.pd: Optimize ~(~X +- Y) into (X -+ Y) [PR94921]
According to my verification proglet, this transformation for signed types
with undefined overflow doesn't introduce nor remove any UB cases, so
should
be valid even for signed integral types.
Not using a for because of the :c on plus which can't be there on minus.
2020-05-06 Jakub Jelinek <jakub@redhat.com>
PR tree-optimization/94921
* match.pd (~(~X - Y) -> X + Y, ~(~X + Y) -> X - Y): New
simplifications.
* gcc.dg/tree-ssa/pr94921.c: New test.
next prev parent reply other threads:[~2020-05-06 9:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-02 12:39 [Bug tree-optimization/94921] New: " gabravier at gmail dot com
2020-05-02 13:09 ` [Bug tree-optimization/94921] " glisse at gcc dot gnu.org
2020-05-04 8:44 ` ubizjak at gmail dot com
2020-05-05 11:44 ` jakub at gcc dot gnu.org
2020-05-05 15:07 ` jakub at gcc dot gnu.org
2020-05-06 9:20 ` cvs-commit at gcc dot gnu.org [this message]
2020-05-06 9:22 ` 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-94921-4-euUUosVv8f@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).