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/99828] inlining failed in call to ‘always_inline’ ‘memcpy’: --param max-inline-insns-auto limit reached Date: Fri, 23 Sep 2022 06:11:16 +0000 [thread overview] Message-ID: <bug-99828-4-m9IaZQwe1x@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99828-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99828 --- Comment #14 from Jiri Slaby <jirislaby at gmail dot com> --- (In reply to Richard Biener from comment #13) > The testcase still does not work on master or with 12.2, thus reconfirmed. Hmm: (In reply to Martin Liška from comment #0) > Noticed by Andi Kleen in kernel, reduced to: > > $ cat 1.i > __attribute__((__always_inline__)) void *memcpy(); > void *foo = memcpy; Provided I cannot reproduce on the current kernel, where exactly does this come from? I see: arch/x86/include/asm/string_64.h: #define __HAVE_ARCH_MEMCPY 1 extern void *memcpy(void *to, const void *from, size_t len); extern void *__memcpy(void *to, const void *from, size_t len); === For KASAN also: #if defined(CONFIG_KASAN) && !defined(__SANITIZE_ADDRESS__) #undef memcpy #define memcpy(dst, src, len) __memcpy(dst, src, len) === arch/x86/lib/memcpy_64.S: SYM_FUNC_START(__memcpy) ... SYM_FUNC_END(__memcpy) ... SYM_FUNC_ALIAS_WEAK(memcpy, __memcpy) === $ nm ../lto/vmlinux|grep -wE '__memcpy|memcpy' ffffffff81dcf0b0 T __memcpy ffffffff81dcf0b0 W memcpy === arch/x86/lib/memcpy_32.c: __used __visible void *memcpy(void *to, const void *from, size_t n) { return __memcpy(to, from, n); }
next prev parent reply other threads:[~2022-09-23 6:11 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-30 13:14 [Bug lto/99828] New: " marxin at gcc dot gnu.org 2021-03-30 13:55 ` [Bug lto/99828] " rguenth at gcc dot gnu.org 2021-03-30 14:01 ` rguenth at gcc dot gnu.org 2021-03-30 17:44 ` andi-gcc at firstfloor dot org 2021-03-30 19:29 ` rguenther at suse dot de 2021-03-30 19:50 ` hubicka at ucw dot cz 2021-03-31 7:22 ` rguenth at gcc dot gnu.org 2021-03-31 9:16 ` hubicka at ucw dot cz 2021-03-31 9:29 ` marxin at gcc dot gnu.org 2021-03-31 10:05 ` rguenther at suse dot de 2021-03-31 11:56 ` marxin at gcc dot gnu.org 2022-09-22 10:58 ` jirislaby at gmail dot com 2022-09-22 10:59 ` jirislaby at gmail dot com 2022-09-22 11:20 ` rguenth at gcc dot gnu.org 2022-09-23 6:11 ` jirislaby at gmail dot com [this message] 2022-09-23 18:11 ` andi at firstfloor dot org 2022-09-23 19:50 ` marxin 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-99828-4-m9IaZQwe1x@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).