public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/106804] Poor codegen for selecting and incrementing value behind a reference
Date: Fri, 02 Sep 2022 06:32:18 +0000 [thread overview]
Message-ID: <bug-106804-4-nZ395OAHUB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106804-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106804
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
Yeah, the sink pass sink_common_stores_to_bb could be enhanced to do this
though it's somewhat questionable when doing so is profitable - it requires
two PHIs, one for the pointer and one for the stored value, which means
possibly two copies on the edge(es) to the common store. In fact I'd say
the reverse transformation is more profitable?
next prev parent reply other threads:[~2022-09-02 6:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 17:11 [Bug c++/106804] New: " anthony.mikh at yandex dot ru
2022-09-01 17:17 ` [Bug middle-end/106804] " pinskia at gcc dot gnu.org
2022-09-01 17:17 ` pinskia at gcc dot gnu.org
2022-09-02 6:32 ` rguenth at gcc dot gnu.org [this message]
2022-09-02 7:18 ` amonakov 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-106804-4-nZ395OAHUB@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: link
Be 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).