public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/91239] gcc generates invalid .debug_macro sections (according to lld folks)
Date: Wed, 20 Apr 2022 10:55:01 +0000 [thread overview]
Message-ID: <bug-91239-4-ElE5Blqf1D@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-91239-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91239
--- Comment #15 from rguenther at suse dot de <rguenther at suse dot de> ---
On Wed, 20 Apr 2022, jakub at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91239
>
> --- Comment #13 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
> No, I can't. For one, many targets GCC supports don't support visibility.
> And, even for those that do, such a change would be effectively an ABI change,
> as mixing *.o files from older gcc version and newer one could result in the
> invalid DW_MACRO_import operands if the old version produced comdat wins.
To avoid that we'd need to change the mangling of the comdat symbol
(add a 'v2' suffix?), so I think it would be feasible.
I agree that it's unfortunate to not have a way to collect unused
symbols after link editing is done. ELF is lacking there - we
get biten by this as well with LTO and hidden symbols used across
LTRANS units - they still consume symtab entries after link editing.
prev parent reply other threads:[~2022-04-20 10:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-91239-4@http.gcc.gnu.org/bugzilla/>
2022-04-19 18:52 ` tromey at gcc dot gnu.org
2022-04-19 20:40 ` tromey at gcc dot gnu.org
2022-04-20 6:59 ` rguenth at gcc dot gnu.org
2022-04-20 7:14 ` jakub at gcc dot gnu.org
2022-04-20 9:06 ` rui314 at gmail dot com
2022-04-20 9:07 ` rui314 at gmail dot com
2022-04-20 9:30 ` jakub at gcc dot gnu.org
2022-04-20 9:39 ` rui314 at gmail dot com
2022-04-20 9:47 ` jakub at gcc dot gnu.org
2022-04-20 9:51 ` rui314 at gmail dot com
2022-04-20 9:56 ` rui314 at gmail dot com
2022-04-20 10:04 ` jakub at gcc dot gnu.org
2022-04-20 10:06 ` rui314 at gmail dot com
2022-04-20 10:55 ` rguenther at suse dot de [this message]
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-91239-4-ElE5Blqf1D@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).