public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/107950] partial LTO linking of libbackend.a: gcc/gcc-rich-location.cc:207: undefined reference to `range_label_for_type_mismatch::get_text(unsigned int) const' Date: Mon, 16 Jan 2023 19:14:03 +0000 [thread overview] Message-ID: <bug-107950-4-tIkhNs68w0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107950-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107950 --- Comment #9 from Jan Hubicka <hubicka at ucw dot cz> --- > > Feel free to grab my initial patch in c#0 and upstream it. I tried that some > time ago in the following email thread: > https://gcc.gnu.org/pipermail/gcc/2021-May/236096.html Actually I was shooting for partial linking LTO streams just to make individual WPAs chaper. With -flinker-output=nolto-rel we are effectively disabling most of benefits of LTO. My main problem was arranging the partial link only when stage1/2 compiler is used so bootstrap works with older GCCs which suports LTO but not partial linking yet. > > > > > I also think it is the case where partial linking makes the symbol to be > > pulled into LTO binary at the initial link time. It should be optimized > > away if linker was not complaining. > > Optimize away during the partial linking? So you think it's a GCC issue when it > comes to partial linking? No with partial linking you merge all the individual object files into single. So if lto frontned is not using some of libbackend entry point, you still get that code biult into it. So I think it is correct behaviour.
next prev parent reply other threads:[~2023-01-16 19:14 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-02 11:56 [Bug bootstrap/107950] New: " marxin at gcc dot gnu.org 2022-12-02 11:58 ` [Bug bootstrap/107950] " marxin at gcc dot gnu.org 2022-12-02 12:07 ` marxin at gcc dot gnu.org 2022-12-02 15:05 ` rguenth at gcc dot gnu.org 2022-12-02 19:08 ` marxin at gcc dot gnu.org 2022-12-02 19:22 ` redi at gcc dot gnu.org 2022-12-02 21:07 ` pinskia at gcc dot gnu.org 2023-01-13 9:27 ` marxin at gcc dot gnu.org 2023-01-14 21:43 ` hubicka at gcc dot gnu.org 2023-01-16 12:35 ` marxin at gcc dot gnu.org 2023-01-16 19:14 ` hubicka at ucw dot cz [this message] 2023-01-19 12:36 ` rguenth at gcc dot gnu.org 2023-01-20 15:16 ` dmalcolm at gcc dot gnu.org 2023-01-23 10:19 ` 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-107950-4-tIkhNs68w0@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).