public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/27800] extra temprorary created when gimplifying return Date: Tue, 07 May 2024 12:20:00 +0000 [thread overview] Message-ID: <bug-27800-4-NP33y1tiGM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-27800-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27800 --- Comment #5 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:bed6ec161be8c5ca2f24195900ce3c9b81c3e141 commit r15-276-gbed6ec161be8c5ca2f24195900ce3c9b81c3e141 Author: Richard Biener <rguenther@suse.de> Date: Tue Feb 20 11:47:03 2024 +0100 middle-end/27800 - avoid unnecessary temporary during gimplification This avoids a tempoary when gimplifying reg = a ? b : c, re-using the LHS of an assignment if that's a register. PR middle-end/27800 * gimplify.cc (gimplify_modify_expr_rhs): For a COND_EXPR avoid a temporary from gimplify_cond_expr when the LHS is a register by pushing the assignment into the COND_EXPR arms. * gcc.dg/pr27800.c: New testcase.
next prev parent reply other threads:[~2024-05-07 12:20 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-27800-4@http.gcc.gnu.org/bugzilla/> 2021-07-24 5:35 ` pinskia at gcc dot gnu.org 2023-02-06 12:16 ` rguenth at gcc dot gnu.org 2024-02-20 10:46 ` rguenth at gcc dot gnu.org 2024-05-07 12:20 ` cvs-commit at gcc dot gnu.org [this message] 2024-05-07 12:20 ` rguenth 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-27800-4-NP33y1tiGM@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).