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 lto/99828] inlining failed in call to ‘always_inline’ ‘memcpy’: --param max-inline-insns-auto limit reached
Date: Tue, 30 Mar 2021 13:55:03 +0000 [thread overview]
Message-ID: <bug-99828-4-TSpVWFztBB@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
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic,
| |missed-optimization
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
The issue is that we do not "merge" the attributes and the memcpy
definition lacks the always_inline attribute, somehow
expand_call_inline then picks up the decl with the attribute set.
I'd argue the 1.i TU is clearly invalid in taking the address of memcpy,
but we don't diagnose this.
How we manage to pick up the attribute in 3.i during WPA / LTRANS remains to be
analyzed. But the "fix" is in the kernel.
next prev parent reply other threads:[~2021-03-30 13:55 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 ` rguenth at gcc dot gnu.org [this message]
2021-03-30 14:01 ` [Bug lto/99828] " 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
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-TSpVWFztBB@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: link
Be 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).