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 c++/106502] Three calls to __attribute__((const)) function
Date: Tue, 02 Aug 2022 10:04:57 +0000	[thread overview]
Message-ID: <bug-106502-4-y45LHWO5VI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106502-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106502

--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
Once you enable optimization a single cat () call remains (as expected).  The
FE does

9931          if (TREE_SIDE_EFFECTS (argarray[0]))
9932            argarray[0] = save_expr (argarray[0]);
9933          t = build_pointer_type (TREE_TYPE (fn));
9934          fn = build_vfn_ref (argarray[0], DECL_VINDEX (fn));

but argarray[0] doesn't have TREE_SIDE_EFFECTS set, it even has TREE_READONLY
set on the CONVERT_EXPR wrapping the call.  Note that save_expr would do
nothing on this tree as well (because TREE_READONLY and !TREE_SIDE_EFFECTS).

  parent reply	other threads:[~2022-08-02 10:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-01 23:04 [Bug c++/106502] New: " redi at gcc dot gnu.org
2022-08-01 23:10 ` [Bug c++/106502] " pinskia at gcc dot gnu.org
2022-08-01 23:11 ` pinskia at gcc dot gnu.org
2022-08-02  6:41 ` redi at gcc dot gnu.org
2022-08-02 10:04 ` rguenth at gcc dot gnu.org [this message]
2022-08-02 10:13 ` redi at gcc dot gnu.org
2022-08-04  2:31 ` egallager at gcc dot gnu.org
2022-08-04  6:27 ` redi 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-106502-4-y45LHWO5VI@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).