public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "slyfox at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/105877] New: GNU strip breaks -flto -g .o files Date: Tue, 07 Jun 2022 18:42:40 +0000 [thread overview] Message-ID: <bug-105877-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105877 Bug ID: 105877 Summary: GNU strip breaks -flto -g .o files Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: lto Assignee: unassigned at gcc dot gnu.org Reporter: slyfox at gcc dot gnu.org CC: hjl.tools at gmail dot com, hubicka at gcc dot gnu.org, marxin at gcc dot gnu.org Target Milestone: --- Host: x86_64-unknown-linux-gnu Initially reported by drnfc on https://github.com/trofi/nix-guix-gentoo/issues/19 where gcc failed to link nix-2.9.0 against stripped liblowdown.a. Both are built with -flto. I'm not sure if it's a strip bug, gcc bug or both. I think (did not check) it used to work long ago. I'm leaning towards gcc bug and filing it here first. Here is a minimal reproducer: // $ cat document.c void lowdown_doc_new(void) {} // $ cat markdown.cc extern "C" { void lowdown_doc_new(void); } int main(){ lowdown_doc_new(); } $ gcc -flto -g -c -o document.o document.c $ cp document.o document-stripped.o $ strip -g document-stripped.o $ g++ markdown.cc -o a document.o -flto-partition=max -flto -g $ g++ markdown.cc -o a document-stripped.o -flto-partition=max -flto -g ld: /tmp/ccajK6YG.ltrans0.ltrans.o:(.debug_info+0x2f): undefined reference to `document.c.20ce96f1' $ gcc -v |& unnix Using built-in specs. COLLECT_GCC=/<<NIX>>/gcc-13.0.0/bin/gcc COLLECT_LTO_WRAPPER=/<<NIX>>/gcc-13.0.0/libexec/gcc/x86_64-unknown-linux-gnu/13.0.0/lto-wrapper Target: x86_64-unknown-linux-gnu Configured with: Thread model: posix Supported LTO compression algorithms: zlib gcc version 13.0.0 20220605 (experimental) (GCC)
next reply other threads:[~2022-06-07 18:42 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-07 18:42 slyfox at gcc dot gnu.org [this message] 2022-06-07 19:08 ` [Bug lto/105877] " hjl.tools at gmail dot com 2022-06-09 10:14 ` hubicka at kam dot mff.cuni.cz 2022-06-13 13:07 ` rguenth at gcc dot gnu.org 2022-06-16 13:27 ` 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-105877-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).