public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/97681] noinline attribute ignored on constexpr function
Date: Mon, 02 Nov 2020 21:15:15 +0000	[thread overview]
Message-ID: <bug-97681-4-kwsZAdNwpA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97681-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
That is not inlining, but just constant expression evaluation. Attempting to
constant evaluate initializers etc. even outside of constant expression is very
important optimization, and noinline attribute has nothing to do with that.

  reply	other threads:[~2020-11-02 21:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-02 21:11 [Bug c++/97681] New: " ldalessandro at gmail dot com
2020-11-02 21:15 ` jakub at gcc dot gnu.org [this message]
2020-11-02 21:17 ` [Bug c++/97681] " ldalessandro at gmail dot com
2020-11-02 21:20 ` jakub at gcc dot gnu.org
2020-11-02 21:28 ` ldalessandro at gmail dot com
2020-11-02 22:42 ` ldalessandro at gmail dot com
2020-11-03  7:23 ` rguenth at gcc dot gnu.org
2020-11-03  9:47 ` jakub at gcc dot gnu.org
2021-11-29  2:05 ` 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-97681-4-kwsZAdNwpA@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).