public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tromey 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: Tue, 19 Apr 2022 18:52:05 +0000 [thread overview]
Message-ID: <bug-91239-4-5gsHlZV0y6@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
Tom Tromey <tromey at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |NEW
CC| |tromey at gcc dot gnu.org
--- Comment #2 from Tom Tromey <tromey at gcc dot gnu.org> ---
I separately discovered this problem when debugging an apparent gdb
slowdown, which I tracked down to a pathological .debug_macro section --
but only when I switched to using 'mold' to link.
> So how does a testcase look like?
[...]
> Can you possibly share two source files and instructions to reproduce the
> conflicting comdats?
I filed a trivial example (three very short files) with mold:
https://github.com/rui314/mold/issues/438
I'm taking the liberty of moving this out of "WAITING".
next parent reply other threads:[~2022-04-19 18:52 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 [this message]
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
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-5gsHlZV0y6@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).