public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mark at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/47819] [meta-bug] LTO debug information issues
Date: Mon, 20 Jul 2020 18:48:43 +0000 [thread overview]
Message-ID: <bug-47819-4-xtFdUw0w1N@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47819-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47819
Mark Wielaard <mark at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Depends on| |88389, 88878, 93117, 91794,
| |93951, 94311
--- Comment #5 from Mark Wielaard <mark at gcc dot gnu.org> ---
(In reply to Mark Wielaard from comment #4)
> The following bugs might be added to this meta-bug. But they seemed not very
> urgent because they involve non-default -g/-f debug flags:
It is probably good for tracking to just add them as dependencies of this
meta-bug whether or not they are "urgent" or not. So I'll just add them all for
now.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88389
[Bug 88389] -flto -g -gsplit-dwarf is broken
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88878
[Bug 88878] .debug_pubnames/types empty with -flto
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91794
[Bug 91794] exception and unwind state is not carried to LTO but controls EH vs
debug frame
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93117
[Bug 93117] -g -flto -fdebug-types-section is broken for units with over 64k
types
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93951
[Bug 93951] [8/9/10/11 Regression] ICE with '-flto -g
-femit-struct-debug-baseonly'
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94311
[Bug 94311] LTO produces line info entries with invalid line numbers
next prev parent reply other threads:[~2020-07-20 18:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-19 22:40 [Bug debug/47819] New: " rguenth at gcc dot gnu.org
2011-02-19 22:44 ` [Bug debug/47819] " rguenth at gcc dot gnu.org
2020-07-17 15:54 ` mark at gcc dot gnu.org
2020-07-20 18:48 ` mark at gcc dot gnu.org [this message]
2021-04-14 7:00 ` rguenth at gcc dot gnu.org
2022-06-01 13:10 ` rguenth 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-47819-4-xtFdUw0w1N@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).