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/99908] SIMD: negating logical + if_else has a suboptimal codegen. Date: Tue, 08 Aug 2023 01:29:46 +0000 [thread overview] Message-ID: <bug-99908-4-K3RE86cOyM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99908-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99908 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED Target Milestone|--- |12.0 --- Comment #10 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Fixed.
prev parent reply other threads:[~2023-08-08 1:29 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-04 12:30 [Bug c++/99908] New: Arm optimisation generates a `not` instruction instead of switching arguments of bsl denis.yaroshevskij at gmail dot com 2021-04-04 20:01 ` [Bug target/99908] SIMD: negating logical + if_else has a suboptimal codegen pinskia at gcc dot gnu.org 2021-04-06 8:04 ` rguenth at gcc dot gnu.org 2021-04-06 9:41 ` crazylht at gmail dot com 2021-04-07 2:12 ` crazylht at gmail dot com 2021-05-07 2:23 ` crazylht at gmail dot com 2021-05-12 11:44 ` cvs-commit at gcc dot gnu.org 2021-05-12 11:45 ` crazylht at gmail dot com 2021-05-12 12:01 ` rearnsha at gcc dot gnu.org 2021-05-12 12:04 ` rearnsha at gcc dot gnu.org 2023-08-08 1:27 ` pinskia at gcc dot gnu.org 2023-08-08 1:29 ` 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-99908-4-K3RE86cOyM@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).