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/96671] Failure to optimize a 3 xor+and pattern to xor+andnot Date: Wed, 18 Nov 2020 19:31:21 +0000 [thread overview] Message-ID: <bug-96671-4-itKsSK0RY4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96671-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96671 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jeff Law <law@gcc.gnu.org>: https://gcc.gnu.org/g:f44e6091627372bd8fc4e72874a003643b021dca commit r11-5146-gf44e6091627372bd8fc4e72874a003643b021dca Author: Eugene Rozenfeld <Eugene.Rozenfeld@microsoft.com> Date: Wed Nov 18 14:29:49 2020 -0500 Optimize two patterns with three xors gcc/ PR tree-optimization/96671 * match.pd (three xor patterns): New patterns.
next prev parent reply other threads:[~2020-11-18 19:31 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-18 7:44 [Bug tree-optimization/96671] New: Failure to optimize a 3 xor+and pattern to xor + andnot gabravier at gmail dot com 2020-08-18 7:45 ` [Bug tree-optimization/96671] Failure to optimize a 3 xor+and pattern to xor+andnot gabravier at gmail dot com 2020-08-18 13:21 ` gabravier at gmail dot com 2020-08-25 10:44 ` rguenth at gcc dot gnu.org 2020-11-18 19:31 ` cvs-commit at gcc dot gnu.org [this message] 2021-01-15 13:26 ` jakub at gcc dot gnu.org 2021-01-15 13:48 ` jakub at gcc dot gnu.org 2021-01-15 18:28 ` cvs-commit at gcc dot gnu.org 2021-01-15 18:29 ` 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-96671-4-itKsSK0RY4@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: linkBe 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).