public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pavel.morozkin at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/105488] New: Function definition is not generated OR function is not inlined Date: Wed, 04 May 2022 22:31:41 +0000 [thread overview] Message-ID: <bug-105488-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105488 Bug ID: 105488 Summary: Function definition is not generated OR function is not inlined Product: gcc Version: 11.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: pavel.morozkin at gmail dot com Target Milestone: --- Note: probably this is a duplicate. This code: inline void f(void) { } int main(void) { f(); } leads to this code: .file "t609.c" .text .def __main; .scl 2; .type 32; .endef .globl main .def main; .scl 2; .type 32; .endef .seh_proc main main: pushq %rbp .seh_pushreg %rbp movq %rsp, %rbp .seh_setframe %rbp, 0 subq $32, %rsp .seh_stackalloc 32 .seh_endprologue call __main call f movl $0, %eax addq $32, %rsp popq %rbp ret .seh_endproc .ident "GCC: (GNU) 11.1.0" .def f; .scl 2; .type 32; .endef Here we see that "call f" is present, while "f:" is absent. As a result: $ gcc t609.c ld: /tmp/cc8z1GjU.o:t609.c:(.text+0xe): undefined reference to `f' collect2: error: ld returned 1 exit status I think that: - either function definition is not generated, - either function is not inlined.
next reply other threads:[~2022-05-04 22:31 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-04 22:31 pavel.morozkin at gmail dot com [this message] 2022-05-04 22:36 ` [Bug c/105488] " pinskia at gcc dot gnu.org 2022-05-04 22:48 ` redi at gcc dot gnu.org 2022-05-05 14:58 ` pavel.morozkin at gmail dot com
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-105488-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).