public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/64801] New: [5 Regression] kernel build failure due to ICF Date: Mon, 26 Jan 2015 14:39:00 -0000 [thread overview] Message-ID: <bug-64801-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64801 Bug ID: 64801 Summary: [5 Regression] kernel build failure due to ICF Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: ipa Assignee: unassigned at gcc dot gnu.org Reporter: trippels at gcc dot gnu.org CC: marxin at gcc dot gnu.org Created attachment 34574 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34574&action=edit unreduced testcase Seen on x86_64 with kernel's defconfig. ... CC init/version.o LD init/built-in.o drivers/built-in.o:psmouse-base.c:function psmouse_extensions: error: undefined reference to 'fsp_detect' -fno-ipa-icf "fixes" the issue. markus@x4 tmp % cat psmouse-base.i int a; int elantech_detect (void) { return -38; } inline int fsp_detect (void) { return -38; } void psmouse_extensions (void) { int (*b)() = fsp_detect; a = b (); } markus@x4 tmp % gcc -c -O2 psmouse-base.i markus@x4 tmp % nm psmouse-base.o| grep fsp_detect U fsp_detect
next reply other threads:[~2015-01-26 14:39 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-26 14:39 trippels at gcc dot gnu.org [this message] 2015-01-26 15:22 ` [Bug ipa/64801] " rguenth at gcc dot gnu.org 2015-01-26 15:50 ` marxin at gcc dot gnu.org 2015-01-27 17:31 ` hubicka at gcc dot gnu.org 2015-01-29 5:30 ` hubicka at gcc dot gnu.org 2015-01-29 5:32 ` hubicka at gcc dot gnu.org 2015-01-29 5:43 ` hubicka at gcc dot gnu.org 2015-01-29 7:43 ` hubicka at gcc dot gnu.org 2015-01-29 7:44 ` hubicka 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-64801-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).