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/108818] [aarch64] use a extra mov instruction compare to llvm Date: Thu, 16 Feb 2023 17:42:21 +0000 [thread overview] Message-ID: <bug-108818-4-gtiLoLpuKn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108818-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108818 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2023-02-16 Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Confirmed, note it is only related to return/argument passing really. That is the following does not produce any extra mov's: ``` void sel(unsigned *X) { *X = *X == 6 ? 6 : 8; } ``` Was this a reducation of a bigger application? Or was it found by making testcases?
prev parent reply other threads:[~2023-02-16 17:42 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-16 10:30 [Bug c/108818] New: " zhongyunde at huawei dot com 2023-02-16 17:31 ` [Bug rtl-optimization/108818] " pinskia at gcc dot gnu.org 2023-02-16 17:42 ` 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-108818-4-gtiLoLpuKn@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).