public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/96692] Failure to optimize xor+or+xor to andnot+xor Date: Tue, 18 Aug 2020 22:12:53 +0000 [thread overview] Message-ID: <bug-96692-4-S5yG9SobPo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96692-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96692 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |enhancement Component|tree-optimization |rtl-optimization --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- This transformation should only happen if there is an andnot instruction. For an example if there is no andnot instruction, there will be 3 dependent instruction while in the first case, there are two independent instructions followed by one dependent ones.
next prev parent reply other threads:[~2020-08-18 22:12 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-18 21:37 [Bug tree-optimization/96692] New: " gabravier at gmail dot com 2020-08-18 22:12 ` pinskia at gcc dot gnu.org [this message] 2020-08-25 10:52 ` [Bug rtl-optimization/96692] " rguenth at gcc dot gnu.org 2022-07-05 16:57 ` cvs-commit at gcc dot gnu.org 2023-02-18 2:01 ` gabravier at gmail dot com 2023-02-18 2:04 ` 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-96692-4-S5yG9SobPo@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).