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 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: Fri, 13 Jan 2023 09:27:56 +0000	[thread overview]
Message-ID: <bug-107950-4-xFwE9MyiDe@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 #6 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #5)
> It might be the case the object files were unused in the archive so they are
> not linked in the LTO front-end but now with using LTO partial linking, they
> are pulled in always.

Yes, that's likely what's happening. So the question is if the issue is caused
by partial linking, or if the function definition should be provided in
libbackend.a itself?

  parent reply	other threads:[~2023-01-13  9:27 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 [this message]
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
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-xFwE9MyiDe@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: link
Be 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).