public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rui314 at gmail dot com" <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:39:52 +0000	[thread overview]
Message-ID: <bug-91239-4-cl41yOPdZg@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 #9 from Rui Ueyama <rui314 at gmail dot com> ---
Thanks Jukub for the description. I'll try to implement it to mold.

One question though. Why doesn't gcc create a weak symbol
wm4.stdio.h.24.5c1b97eef3c86b7a2549420f69f4f128 at the beginning of each
wm4.stdio.h.24.5c1b97eef3c86b7a2549420f69f4f128 section and always use that
symbol instead of referring the beginning of the section using the section
symbol? The ELF spec says that no one should refer any comdat members directly
and instead refer them via symbols, so the current GCC's behavior violates the
spec if I understand it correctly.

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

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