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 ipa/113203] __attribute__ ((always_inline)) fails with C99/LTO/-Og. Date: Mon, 08 Jan 2024 09:16:06 +0000 [thread overview] Message-ID: <bug-113203-4-HkOEBiyjdf@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 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |documentation CC| |hubicka at gcc dot gnu.org --- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> --- With -Og we specifically disable IPA inlining, not considering that always-inline functions might only appear with LTO. I don't think that cross-TU "always-inline" is sensible, and we probably should not merge the always-inline definition with the not always-inline declaration that's effective for the call in question. So we should accept the code at compile-time but not honor always-inline cross-TU in the way it is presented by the testcase. The bool f(int); declaration should force an out-of-line copy of the C99 inline, right? And GCC always-inline doesn't change that? Btw, the same should happen with -O2 -flto but __attribute__((optimize(0))) on main(). It might be worth amending the always-inline documentation as well.
prev parent reply other threads:[~2024-01-08 9:16 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 2024-01-03 16:26 ` stefan at bytereef dot org 2024-01-08 9:16 ` rguenth at gcc dot gnu.org [this message]
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-HkOEBiyjdf@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).