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 ipa/113203] __attribute__ ((always_inline)) fails with C99/LTO/-Og.
Date: Wed, 03 Jan 2024 08:35:25 +0000	[thread overview]
Message-ID: <bug-113203-4-BYQy5rQHj3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113203-4@http.gcc.gnu.org/bugzilla/>

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

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

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

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
If you want to make something always_inline, define it in the header rather
than having just a non-always_inline declaration in the header and definition
in some TU.
Because without LTO that means it will never be actually attempted to be
inlined, and with LTO it can't be inlined until the IPA inlining which -O0 or
-Og don't perform.
Or, if the intention is that all calls to the function within its TU are
inlined and not the other ones, split the function into two, one always_inline
which is used from within the TU and another one which just calls it and is
used from other TUs.

  parent reply	other threads:[~2024-01-03  8:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-02 16:54 [Bug c/113203] New: " stefan at bytereef dot org
2024-01-03  1:57 ` [Bug ipa/113203] " pinskia at gcc dot gnu.org
2024-01-03  2:05 ` pinskia at gcc dot gnu.org
2024-01-03  8:35 ` jakub at gcc dot gnu.org [this message]
2024-01-03 16:26 ` stefan at bytereef dot org
2024-01-08  9:16 ` 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-113203-4-BYQy5rQHj3@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).