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 tree-optimization/115679] inlining failed in call to 'foo': function not considered for inlining
Date: Thu, 27 Jun 2024 12:32:33 +0000	[thread overview]
Message-ID: <bug-115679-4-CW1WedikI1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115679-4@http.gcc.gnu.org/bugzilla/>

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hubicka at gcc dot gnu.org,
                   |                            |rguenth at gcc dot gnu.org

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
With -Og it's usually that the always-inline function is called indirectly -
that's an unsupported case.

  reply	other threads:[~2024-06-27 12:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-27 10:45 [Bug tree-optimization/115679] New: " Changqing.Li at windriver dot com
2024-06-27 12:32 ` rguenth at gcc dot gnu.org [this message]
2024-06-27 13:38 ` [Bug tree-optimization/115679] " hubicka at ucw dot cz
2024-06-27 19:40 ` pinskia at gcc dot gnu.org
2024-07-03  0:57 ` Changqing.Li at windriver dot com
2024-07-03  0:59 ` Changqing.Li at windriver dot com
2024-07-03  1:05 ` pinskia at gcc dot gnu.org
2024-07-03  1:19 ` Changqing.Li at windriver dot com
2024-07-03  4:52 ` pinskia at gcc dot gnu.org
2024-07-03  4:58 ` 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-115679-4-CW1WedikI1@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).