From: Alexandre Oliva <oliva@adacore.com>
To: Richard Biener <rguenther@suse.de>
Cc: Bernd Edlinger <bernd.edlinger@hotmail.de>,
"gcc-patches\@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Jakub Jelinek <jakub@redhat.com>
Subject: Re: [PATCH] Add line debug info for virtual thunks (PR ipa/97937)
Date: Wed, 06 Jan 2021 04:01:53 -0300 [thread overview]
Message-ID: <or35ze4kgu.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <nycvar.YFH.7.76.2101051322560.17979@zhemvz.fhfr.qr> (Richard Biener's message of "Tue, 5 Jan 2021 13:26:39 +0100 (CET)")
On Jan 5, 2021, Richard Biener <rguenther@suse.de> wrote:
> But isn't this a consumer issue then? If there is no line info for
> a PC range then gdb shouldn't display any.
No, there *is* line info there, carried over from an earlier .loc
directive, as there isn't anything like ".noloc" to output with a
function that is not expected or supposed to have line number info.
Without that, the assembler just extends the previous .loc directive
onto the function.
--
Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/
Free Software Activist GNU Toolchain Engineer
Vim, Vi, Voltei pro Emacs -- GNUlius Caesar
next prev parent reply other threads:[~2021-01-06 7:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 20:06 Bernd Edlinger
2021-01-04 21:45 ` Jeff Law
2021-01-06 7:52 ` Bernd Edlinger
2021-01-05 12:26 ` Richard Biener
2021-01-06 7:01 ` Alexandre Oliva [this message]
2021-01-06 7:36 ` Bernd Edlinger
2021-01-06 7:50 ` Richard Biener
2021-01-06 10:07 ` Jakub Jelinek
2021-01-07 7:27 ` Richard Biener
2021-01-05 13:09 ` Alexandre Oliva
2021-01-06 11:49 ` Eric Botcazou
2021-01-06 12:26 ` Bernd Edlinger
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=or35ze4kgu.fsf@lxoliva.fsfla.org \
--to=oliva@adacore.com \
--cc=bernd.edlinger@hotmail.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=rguenther@suse.de \
/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).