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 middle-end/111373] conditional selection gives bad code generation Date: Mon, 11 Sep 2023 16:55:17 +0000 [thread overview] Message-ID: <bug-111373-4-I2ApIXmtj6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111373-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111373 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed|2023-09-11 00:00:00 | Summary|conditional " |conditional selection gives | |bad code generation --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- In this case we have this right before expand: if (v$2_9 < v$1_25) goto <bb 7>; [INV] else goto <bb 8>; [INV] <bb 7> : <bb 8> : # a$1_65 = PHI <a$1_64(6), a$2_66(7)> # a$2_67 = PHI <a$2_66(6), a$1_64(7)> But this is a conditional move. The biggest issue here is that GCC is not detecting this as a conditional move though. And then make really bad register allocation decisions due to that.
next prev parent reply other threads:[~2023-09-11 16:55 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-11 16:38 [Bug rtl-optimization/111373] New: Register moves right before stores and return tkoenig at gcc dot gnu.org 2023-09-11 16:54 ` [Bug middle-end/111373] conditional " pinskia at gcc dot gnu.org 2023-09-11 16:55 ` pinskia at gcc dot gnu.org [this message] 2023-09-11 16:56 ` [Bug middle-end/111373] conditional selection gives bad code generation pinskia at gcc dot gnu.org 2023-09-11 16:59 ` 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-111373-4-I2ApIXmtj6@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).