public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Patrick Palka <ppalka@redhat.com>
Cc: Jason Merrill <jason@redhat.com>,
	gcc-patches List <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] c++: quadratic constexpr behavior for left-assoc logical exprs [PR102780]
Date: Tue, 26 Oct 2021 23:11:08 +0200	[thread overview]
Message-ID: <20211026211108.GE304296@tucnak> (raw)
In-Reply-To: <99c81449-d68a-31c8-2ce6-fff154508c9@idea>

On Tue, Oct 26, 2021 at 05:07:43PM -0400, Patrick Palka wrote:
> The performance impact of the other calls to cxx_eval_outermost_const_expr
> from p_c_e_1 is probably already mostly mitigated by the constexpr call
> cache and the fact that we try to evaluate all calls to constexpr
> functions during cp_fold_function anyway (at least with -O).  So trial

constexpr function bodies don't go through cp_fold_function (intentionally,
so that we don't optimize away UB), the bodies are copied before the trees of the
normal copy are folded.

	Jakub


  reply	other threads:[~2021-10-26 21:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26 17:44 Patrick Palka
2021-10-26 18:45 ` Jakub Jelinek
2021-10-26 19:29   ` Jason Merrill
2021-10-26 20:01     ` Jakub Jelinek
2021-10-26 21:07     ` Patrick Palka
2021-10-26 21:11       ` Jakub Jelinek [this message]
2021-10-27 18:54         ` Patrick Palka
2021-10-27 20:37           ` Jason Merrill
2021-10-27 21:10             ` Patrick Palka
2021-10-27 21:51               ` Jason Merrill
2021-10-28 16:40                 ` Patrick Palka
2021-10-28 17:38                   ` Jakub Jelinek
2021-10-28 19:35                     ` Patrick Palka
2021-10-29 11:59                       ` Jakub Jelinek
2021-11-01 18:45                         ` Patrick Palka
2021-11-01 19:08                           ` Patrick Palka

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=20211026211108.GE304296@tucnak \
    --to=jakub@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jason@redhat.com \
    --cc=ppalka@redhat.com \
    /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).