public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/99618] New: `.gnu.debuglto_.debug_macro' referenced in section `.gnu.debuglto_.debug_macro' of X defined in discarded section Date: Tue, 16 Mar 2021 13:11:57 +0000 [thread overview] Message-ID: <bug-99618-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99618 Bug ID: 99618 Summary: `.gnu.debuglto_.debug_macro' referenced in section `.gnu.debuglto_.debug_macro' of X defined in discarded section Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: lto Assignee: unassigned at gcc dot gnu.org Reporter: marxin at gcc dot gnu.org CC: marxin at gcc dot gnu.org, rguenth at gcc dot gnu.org Target Milestone: --- I'm not sure if it's problem at compiler or linker side. Reduced from perf package: $ cat 1.i ; # 1 "/usr/include/bits/wordsize.h" 1 #define __WORDSIZE 64 #define __WORDSIZE_TIME64_COMPAT32 1 $ gcc -flto -ggdb3 -c -fPIC -g 1.i && cp 1.o 2.o && gcc -r -o libperf-in.o [12].o -fuse-ld=bfd `.gnu.debuglto_.debug_macro' referenced in section `.gnu.debuglto_.debug_macro' of /tmp/ccnBoXGI.debug.temp.o: defined in discarded section `.gnu.debuglto_.debug_macro[wm4.wordsize.h.1.b68ef8235bd466c01307f942f7f51e04]' of /tmp/ccnBoXGI.debug.temp.o collect2: error: ld returned 1 exit status While ld.gold is fine: $ gcc -flto -ggdb3 -c -fPIC -g 1.i && cp 1.o 2.o && gcc -r -o libperf-in.o [12].o -fuse-ld=gold
next reply other threads:[~2021-03-16 13:11 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-16 13:11 marxin at gcc dot gnu.org [this message] 2021-03-16 13:23 ` [Bug lto/99618] " rguenth at gcc dot gnu.org 2021-03-16 13:26 ` marxin at gcc dot gnu.org 2021-03-17 13:33 ` hjl.tools at gmail dot com 2021-03-17 13:41 ` rguenth at gcc dot gnu.org 2021-03-17 13:44 ` rguenth at gcc dot gnu.org 2021-03-17 13:44 ` jakub at gcc dot gnu.org 2021-03-17 13:49 ` hjl.tools at gmail dot com 2021-03-17 13:51 ` [Bug debug/99618] " hjl.tools at gmail dot com 2021-03-17 13:54 ` hjl.tools at gmail dot com 2021-03-17 13:56 ` rguenth at gcc dot gnu.org 2021-03-17 13:59 ` jakub at gcc dot gnu.org 2021-03-17 14:08 ` rguenth at gcc dot gnu.org 2021-03-17 14:10 ` rguenth at gcc dot gnu.org 2021-03-17 14:12 ` jakub at gcc dot gnu.org 2021-03-17 14:12 ` rguenth at gcc dot gnu.org 2021-03-17 14:29 ` hjl.tools at gmail dot com 2021-03-17 14:32 ` jakub at gcc dot gnu.org 2021-03-17 15:54 ` jakub at gcc dot gnu.org 2021-03-17 18:09 ` marxin at gcc dot gnu.org 2021-03-17 22:45 ` hjl.tools 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-99618-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).