public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lveyde at redhat dot com" <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 23:49:14 +0000	[thread overview]
Message-ID: <bug-108905-4-rNFyMgtiys@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

--- Comment #2 from Lev Veyde <lveyde at redhat dot com> ---
So the incorrect filename and line comes from not setting it properly in inline
assembly the macro resolves to?

So it's basically an issue in the Linux kernel source code?

I tried to add .line to the inline assembly code and it didn't really had any
effect on the compiled kernel, as far as debugging info for the symbol is
concerned. However I'm not 100% certain that I did it correctly.

      parent reply	other threads:[~2023-02-23 23:49 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 ` [Bug debug/108905] Debugging information refers to the wrong file with function defined in toplevel inline-asm pinskia at gcc dot gnu.org
2023-02-23 23:49 ` lveyde at redhat dot com [this message]

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-rNFyMgtiys@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).