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 lto/114241] False-positive -Wodr warning when using -flto and -fno-semantic-interposition
Date: Wed, 06 Mar 2024 09:16:13 +0000	[thread overview]
Message-ID: <bug-114241-4-QdfzqBNpdE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114241-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114241

--- Comment #2 from Jan Hubicka <hubicka at ucw dot cz> ---
This indeed looks like bug caused by fact that the class is keyed into
one of the two units.

Outputting translation unit names is unfortunately hard, since they are
object files and often comming from .a archive where we know only
offset, but no original file name or something.

I had patch which passed through original filename attached to
TRALSATION_UNIT_DECL, but it also had problems, i.e. printing relative
filenames from wrong directory.

  parent reply	other threads:[~2024-03-06  9:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-05 15:38 [Bug lto/114241] New: " abbeyj+gcc at gmail dot com
2024-03-06  7:46 ` [Bug lto/114241] " rguenth at gcc dot gnu.org
2024-03-06  9:16 ` hubicka at ucw dot cz [this message]
2024-03-06  9:18 ` hubicka 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-114241-4-QdfzqBNpdE@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).