public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dthorn at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/106725] LTO semantics for __attribute__((leaf))
Date: Thu, 25 Aug 2022 16:26:16 +0000	[thread overview]
Message-ID: <bug-106725-4-bmR117wkMU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106725-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Daniel Thornburgh <dthorn at google dot com> ---
(In reply to rguenther@suse.de from comment #3)
> As said, GCC shouldn't assume this since leaf is defined at translation
> unit level, not at LTO level.

Sure, but what prevents GCC from making this assumption? Are all uses of leaf
evaluated before the TUs are merged? Does GCC have some provenance tracking for
which TU a given function came from in the merged view? Is there a pass I
missed to drop leaf after merging but before it's used?

  parent reply	other threads:[~2022-08-25 16:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-106725-4@http.gcc.gnu.org/bugzilla/>
2022-08-24  7:18 ` rguenth at gcc dot gnu.org
2022-08-24 16:42 ` dthorn at google dot com
2022-08-25  5:48 ` rguenther at suse dot de
2022-08-25 16:26 ` dthorn at google dot com [this message]
2022-08-26  7:15 ` rguenther at suse dot de
2022-11-01  1:32 ` dthorn at google dot com
2022-11-01  1:50 ` dthorn at google dot com
2022-11-05 14:09 ` 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-106725-4-bmR117wkMU@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).