public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/94469] lto abstract variable emitted as concrete decl (ada test-case)
Date: Tue, 07 Apr 2020 15:27:56 +0000 [thread overview]
Message-ID: <bug-94469-4-To9Jfz2BPL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94469-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94469
--- Comment #16 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #14)
> Using DW_AT_declaration for variables and CUs instead of PUs is IMHO the
> most promising approach then.
I managed to reproduce the "Multiple matches" problem by switching the language
for the dwarf assembly test-case to ada (and using -readnow). And adding the
DW_AT_declaration at the concrete DIE fixed that problem. So yeah, that looks
promising.
next prev parent reply other threads:[~2020-04-07 15:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 13:22 [Bug debug/94469] New: " vries at gcc dot gnu.org
2020-04-06 6:08 ` [Bug debug/94469] " rguenth at gcc dot gnu.org
2020-04-06 9:32 ` vries at gcc dot gnu.org
2020-04-06 9:35 ` rguenth at gcc dot gnu.org
2020-04-06 9:49 ` vries at gcc dot gnu.org
2020-04-06 9:54 ` vries at gcc dot gnu.org
2020-04-06 9:56 ` rguenth at gcc dot gnu.org
2020-04-06 10:44 ` rguenth at gcc dot gnu.org
2020-04-06 11:27 ` vries at gcc dot gnu.org
2020-04-06 11:38 ` rguenth at gcc dot gnu.org
2020-04-06 11:50 ` rguenth at gcc dot gnu.org
2020-04-07 12:09 ` vries at gcc dot gnu.org
2020-04-07 12:22 ` rguenther at suse dot de
2020-04-07 13:53 ` vries at gcc dot gnu.org
2020-04-07 14:09 ` rguenth at gcc dot gnu.org
2020-04-07 15:18 ` vries at gcc dot gnu.org
2020-04-07 15:27 ` vries at gcc dot gnu.org [this message]
2020-04-08 10:47 ` 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-94469-4-To9Jfz2BPL@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).