public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/111437] Some always inline functions are incorrectly warn of as "might not be inlinable" Date: Sun, 17 Sep 2023 06:37:13 +0000 [thread overview] Message-ID: <bug-111437-4-3TgkoiAPER@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111437-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111437 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED Resolution|--- |INVALID --- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> --- One definition has: __attribute__((hot)) __attribute__((always_inline)) pawd pawmsg_SIGKILL( pawexe pid ) { return pawtrigger( # 127 "/mnt/CODE/gitlab/dragonbuilder/include/paw/pawint/../pawmsg.h" 3 4 ((void *)0) # 127 "/mnt/CODE/gitlab/dragonbuilder/include/paw/pawint/../pawmsg.h" , PAWMSGID_KILL_NOW, PAWMSG_CLSID_APP, 0, pid ); } Yes without inline the always_inline might be not be inlinable ... The preprocessed source is full of issues; redefinitions: /mnt/CODE/gitlab/dragonbuilder/src/libpaw/pawaio.c:50:28: error: redefinition of ‘pawabspath_putroot’ In file included from /mnt/CODE/gitlab/dragonbuilder/src/libpaw/libpaw.h:19, from /mnt/CODE/gitlab/dragonbuilder/src/libpaw/pawaio.c:1: /mnt/CODE/gitlab/dragonbuilder/include/paw/pawaio.h:554:28: note: previous definition of ‘pawabspath_putroot’ with type ‘pawjd(pawmbcd *, pawmbctxt, pawmbctxt)’ {aka ‘long int(pawmbcd *, pawmbc_txt, pawmbc_txt)’} etc. But the pattern for the "might not be inlinable" is all the same as what I mentioned first. There is only always_inline without an inline ...
next prev parent reply other threads:[~2023-09-17 6:37 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-16 21:53 [Bug c/111437] New: " gb2985 at gmail dot com 2023-09-16 22:14 ` [Bug c/111437] " pinskia at gcc dot gnu.org 2023-09-17 6:19 ` [Bug ipa/111437] " gb2985 at gmail dot com 2023-09-17 6:22 ` gb2985 at gmail dot com 2023-09-17 6:37 ` pinskia at gcc dot gnu.org [this message] 2023-09-17 6:47 ` gb2985 at gmail dot com 2023-09-17 8:03 ` schwab@linux-m68k.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-111437-4-3TgkoiAPER@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).