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/108905] Debugging information refers to the wrong file with function defined in toplevel inline-asm
Date: Thu, 23 Feb 2023 15:40:12 +0000 [thread overview]
Message-ID: <bug-108905-4-31hWin5BtF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108905-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108905
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Debugging information |Debugging information
|refers to the wrong file |refers to the wrong file
| |with function defined in
| |toplevel inline-asm
Keywords| |inline-asm
Component|c |debug
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
GCC does not generate debug info for top level inline-asm. It is up to the user
of such things to do the .line, .file, etc.
So I think this is not a bug overall.
next prev parent reply other threads:[~2023-02-23 15:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 15:22 [Bug c/108905] New: Debugging information refers to the wrong file lveyde at redhat dot com
2023-02-23 15:40 ` pinskia at gcc dot gnu.org [this message]
2023-02-23 23:49 ` [Bug debug/108905] Debugging information refers to the wrong file with function defined in toplevel inline-asm lveyde at redhat dot com
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-108905-4-31hWin5BtF@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).