public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "m.cencora at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/104597] New: LTO does not inline indirect call Date: Fri, 18 Feb 2022 13:29:27 +0000 [thread overview] Message-ID: <bug-104597-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104597 Bug ID: 104597 Summary: LTO does not inline indirect call Product: gcc Version: 11.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: m.cencora at gmail dot com Target Milestone: --- Given following files: // main.cpp using intfunc = int (*)(); intfunc getIntFunc(int i); namespace { int test() { auto func = getIntFunc(1); return func(); } } int main() { return test(); } // lib1.cpp namespace { int getInt0() { return 0; } int getInt1() { return 1; } int getInt2() { return 2; } } using intfunc = int (*)(); intfunc getIntFunc(int i) { if (i == 0) { return getInt0; } else if (i == 1) { return getInt1; } else if (i == 2) { return getInt2; } __builtin_abort(); } and compilation with: g++ -std=c++20 -Wall -Wextra -O3 -flto -fvisibility=hidden -fvisibility-inlines-hidden -ffunction-sections -Wl,-gc-sections main.cpp lib1.cpp -o test Call to getInt1 does not get inlined: Dump of assembler code for function main: 0x0000000000001040 <+0>: endbr64 0x0000000000001044 <+4>: jmp 0x1140 <_ZN12_GLOBAL__N_17getInt1Ev>
next reply other threads:[~2022-02-18 13:29 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-18 13:29 m.cencora at gmail dot com [this message] 2022-02-18 13:34 ` [Bug c++/104597] " m.cencora at gmail dot com 2022-02-18 13:52 ` m.cencora at gmail dot com 2022-02-19 0:28 ` [Bug ipa/104597] " pinskia at gcc dot gnu.org 2022-02-21 9:37 ` 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-104597-4@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).