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 target/116013] Missed optimization opportunity with andn involving consts Date: Tue, 23 Jul 2024 05:32:21 +0000 [thread overview] Message-ID: <bug-116013-4-08TlSA6co9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-116013-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116013 --- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Note I attached my patches to PR 115086 which fixes this for aarch64. All that is needed after these patches get approved is either rename the current patterns in the i386 backend to be andn<mode>3 and iorn<mode>3 and it will work correctly. even for vector modes.
prev parent reply other threads:[~2024-07-23 5:32 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-07-20 10:46 [Bug tree-optimization/116013] New: " bisqwit at iki dot fi 2024-07-20 14:19 ` [Bug middle-end/116013] " bisqwit at iki dot fi 2024-07-22 7:06 ` [Bug target/116013] " rguenth at gcc dot gnu.org 2024-07-23 2:27 ` pinskia at gcc dot gnu.org 2024-07-23 2:29 ` pinskia at gcc dot gnu.org 2024-07-23 2:45 ` pinskia at gcc dot gnu.org 2024-07-23 5:32 ` pinskia at gcc dot gnu.org [this message]
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-116013-4-08TlSA6co9@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).