public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <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 09:47:46 +0000	[thread overview]
Message-ID: <bug-91239-4-JyVt5WTWVt@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 #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
See the PR I've referred to.
There is no ABI that would cover the names of such symbols and we definitely
don't want them to be visible out of the shared libraries or binaries.

  parent reply	other threads:[~2022-04-20  9:47 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 [this message]
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

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-JyVt5WTWVt@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).