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/112657] missed optimization: cmove not used with multiple returns Date: Tue, 21 Nov 2023 21:53:13 +0000 [thread overview] Message-ID: <bug-112657-4-3Pcsj6Rjp9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112657-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112657 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- It is converted to a csel on aarch64 so it is either ifcvt.cc rejecting the issue or a tuning issue with the x86_64 backend. x86_64: ``` IF-THEN-JOIN block found, pass 1, test 2, then 3, join 4 ========== no more changes 1 possible IF blocks searched. 0 IF blocks converted. 0 true changes made. ``` vs aarch64: ``` IF-THEN-JOIN block found, pass 1, test 2, then 3, join 4 scanning new insn with uid = 30. scanning new insn with uid = 31. scanning new insn with uid = 32. if-conversion succeeded through noce_try_cmove ... ```
next prev parent reply other threads:[~2023-11-21 21:53 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-21 21:42 [Bug tree-optimization/112657] New: " goon.pri.low at gmail dot com 2023-11-21 21:53 ` pinskia at gcc dot gnu.org [this message] 2023-11-21 21:53 ` [Bug target/112657] " pinskia at gcc dot gnu.org 2023-11-21 21:59 ` [Bug rtl-optimization/112657] [13/14 Regression] " pinskia at gcc dot gnu.org 2023-11-22 9:16 ` ubizjak at gmail dot com 2023-11-22 9:28 ` ubizjak at gmail dot com 2023-11-22 9:38 ` ubizjak at gmail dot com 2023-11-22 9:46 ` ubizjak at gmail dot com 2023-11-22 10:48 ` rguenth at gcc dot gnu.org 2023-11-22 13:35 ` hubicka at gcc dot gnu.org 2024-03-07 21:01 ` law at gcc dot gnu.org 2024-05-21 9:18 ` [Bug rtl-optimization/112657] [13/14/15 " 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-112657-4-3Pcsj6Rjp9@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).