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 lto/107014] flatten+lto fails the kernel build
Date: Fri, 23 Sep 2022 08:04:46 +0000	[thread overview]
Message-ID: <bug-107014-4-ZoQgZDiQYg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107014-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
The whole point of "flatten" is that there's _no_ limit.  Looking at the
function I don't see why you'd ever use that?

If the desire is to force inlining a specific call then I think there's
currently
no good way to get that.  It doesn't seem to be possible to use an
always-inline
alias to get this behavior at least.  Some not existing #pragma GCC inline
might be a better solution than "flatten".

But as said, I'd just remove "flatten" - is it known what it was added for?

  parent reply	other threads:[~2022-09-23  8:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23  7:38 [Bug lto/107014] New: flatten+lto jirislaby at gmail dot com
2022-09-23  7:55 ` [Bug lto/107014] flatten+lto fails the kernel build marxin at gcc dot gnu.org
2022-09-23  8:04 ` rguenth at gcc dot gnu.org [this message]
2022-09-23  8:21 ` amonakov at gcc dot gnu.org
2022-09-23  8:24 ` jirislaby at gmail dot com
2022-09-23  8:28 ` amonakov at gcc dot gnu.org
2022-09-23  9:52 ` jirislaby at gmail dot com
2022-09-23 10:12 ` amonakov at gcc dot gnu.org
2022-09-23 10:36 ` jakub at gcc dot gnu.org
2022-09-25 19:56 ` andi-gcc at firstfloor dot 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-107014-4-ZoQgZDiQYg@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).