public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/96385] GCC generates separate debug info with undefined symbols without relocations Date: Fri, 31 Jul 2020 15:27:27 +0000 [thread overview] Message-ID: <bug-96385-4-FZGIYqIBdq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96385-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96385 --- Comment #7 from H.J. Lu <hjl.tools at gmail dot com> --- [hjl@gnu-cfl-2 pr26324]$ cat pr15146a.c extern int xxx; int bar (void) { return xxx; } int main () { return 0; } [hjl@gnu-cfl-2 pr26324]$ cat pr15146b.c int xxx = 3; [hjl@gnu-cfl-2 pr26324]$ cat pr15146c.c [hjl@gnu-cfl-2 pr26324]$ make gcc -B./ -O2 -g -o x -Wl,-R,. \ -Wl,--no-copy-dt-needed-entries -Wl,--no-as-needed pr15146a.o pr15146c.so ./ld: /tmp/ccHirkTe.debug.temp.o: undefined reference to symbol 'xxx' ./ld: ./pr15146b.so: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status make: *** [Makefile:15: x] Error 1 [hjl@gnu-cfl-2 pr26324]$
next prev parent reply other threads:[~2020-07-31 15:27 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-29 21:47 [Bug lto/96385] New: " hjl.tools at gmail dot com 2020-07-30 6:15 ` [Bug lto/96385] " rguenth at gcc dot gnu.org 2020-07-30 8:30 ` rguenth at gcc dot gnu.org 2020-07-30 11:48 ` hjl.tools at gmail dot com 2020-07-30 12:02 ` rguenther at suse dot de 2020-07-30 12:05 ` rguenther at suse dot de 2020-07-30 12:17 ` hjl.tools at gmail dot com 2020-07-31 15:26 ` hjl.tools at gmail dot com 2020-07-31 15:27 ` hjl.tools at gmail dot com [this message] 2020-07-31 19:56 ` hjl.tools at gmail dot com 2020-08-01 1:12 ` hjl.tools at gmail dot com 2020-08-01 1:15 ` hjl.tools at gmail dot com 2020-08-02 12:40 ` [Bug lto/96385] [8/9/10/11 Regression] " hjl.tools at gmail dot com 2020-08-03 6:58 ` rguenth at gcc dot gnu.org 2020-08-03 7:41 ` rguenth at gcc dot gnu.org 2020-08-03 7:53 ` rguenth at gcc dot gnu.org 2020-08-03 8:02 ` rguenth at gcc dot gnu.org 2020-08-03 12:22 ` amodra at gmail dot com 2020-08-03 13:09 ` cvs-commit at gcc dot gnu.org 2020-08-03 13:10 ` [Bug lto/96385] [8/9/10 " rguenth at gcc dot gnu.org 2020-08-03 13:10 ` rguenth at gcc dot gnu.org 2020-09-11 12:12 ` cvs-commit at gcc dot gnu.org 2020-09-11 12:18 ` [Bug lto/96385] [8/9 " rguenth at gcc dot gnu.org 2021-04-12 11:23 ` cvs-commit at gcc dot gnu.org 2021-04-26 10:46 ` [Bug lto/96385] [8 " cvs-commit at gcc dot gnu.org 2021-04-26 10:48 ` rguenth 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-96385-4-FZGIYqIBdq@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).