public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jirislaby at gmail dot com" <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:24:31 +0000 [thread overview] Message-ID: <bug-107014-4-2KXqWz5Npi@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 #4 from Jiri Slaby <jirislaby at gmail dot com> --- (In reply to Alexander Monakov from comment #3) > It was added to force inlining of small helpers that outgrow limits when > building with gcov profiling: (with clang) > I am surprised that "flatten" blows up on this function. Is that with any > config, or again some specific settings like gcov? Is there an existing lkml > thread about this? Yes, linked in the commit log: https://lore.kernel.org/all/CAK8P3a2ZWfNeXKSm8K_SUhhwkor17jFo3xApLXjzfPqX0eUDUA@mail.gmail.com/
next prev parent reply other threads:[~2022-09-23 8:24 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 2022-09-23 8:21 ` amonakov at gcc dot gnu.org 2022-09-23 8:24 ` jirislaby at gmail dot com [this message] 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-2KXqWz5Npi@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: linkBe 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).