public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/105089] CTF for a defined extern variable is ambiguous
Date: Tue, 29 Mar 2022 16:11:13 +0000 [thread overview]
Message-ID: <bug-105089-4-TeoVLscC0I@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105089-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105089
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Indu Bhagat from comment #2)
> Regarding this above-mentioned case of two variables (one inside the
> function), CTF emits debug information for file-scope and global-scope
> variables only. So in this example, the declaration of a inside the function
> should not be considered from CTF perspective.
But a is in the global scope ....
Just not injected into the global scope for that translation unit.
next prev parent reply other threads:[~2022-03-29 16:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 18:41 [Bug debug/105089] New: " ibhagat at gcc dot gnu.org
2022-03-29 7:39 ` [Bug debug/105089] " rguenth at gcc dot gnu.org
2022-03-29 15:58 ` ibhagat at gcc dot gnu.org
2022-03-29 16:00 ` ibhagat at gcc dot gnu.org
2022-03-29 16:11 ` pinskia at gcc dot gnu.org [this message]
2022-03-29 17:12 ` ibhagat at gcc dot gnu.org
2022-04-14 17:37 ` cvs-commit at gcc dot gnu.org
2022-04-14 17:37 ` cvs-commit at gcc dot gnu.org
2023-03-16 21:41 ` ibhagat 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-105089-4-TeoVLscC0I@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).