From: Tom Tromey <tom@tromey.com>
To: Alan Hayward <Alan.Hayward@arm.com>
Cc: Simon Marchi <simark@simark.ca>,
"gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>,
nd <nd@arm.com>
Subject: Re: [PATCH 1/2] Allow function prologues to have multiple repeating lines
Date: Fri, 30 Nov 2018 20:10:00 -0000 [thread overview]
Message-ID: <87efb2mimz.fsf@tromey.com> (raw)
In-Reply-To: <0BDE5F6A-06E9-4246-A1C6-1F8E0F22C983@arm.com> (Alan Hayward's message of "Mon, 5 Nov 2018 16:04:35 +0000")
>>>>> "Alan" == Alan Hayward <Alan.Hayward@arm.com> writes:
[...]
Alan> So, I don’t think it’s possible to tell apart the first example with the final
Alan> example.
What does the DWARF look like?
Ideally I think gdb would just rely on the DWARF to mark the end of the
prologue. However, of course that can't always be done -- but I would
much rather have a blacklist of bad compilers than the current approach
of a whitelist of good ones; and I'm wondering if that is achievable at
all. Maybe doing this well would mean exposing a bit more info from the
DWARF to gdb's line table -- but that seems totally fine.
Maybe I'm really not understanding the problem, feel free to say so :)
But I'd like to understand better; my own forays into this area haven't
turned out so well.
thanks,
Tom
prev parent reply other threads:[~2018-11-30 20:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-24 9:04 Alan Hayward
2018-10-24 9:04 ` [PATCH 2/2] Check for line notes on GCC as well as Clang Alan Hayward
2018-11-05 4:16 ` Simon Marchi
2018-10-31 16:26 ` [PING][PATCH 1/2] Allow function prologues to have multiple repeating lines Alan Hayward
2018-11-05 3:50 ` [PATCH " Simon Marchi
2018-11-05 16:04 ` Alan Hayward
2018-11-30 20:10 ` Tom Tromey [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=87efb2mimz.fsf@tromey.com \
--to=tom@tromey.com \
--cc=Alan.Hayward@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=nd@arm.com \
--cc=simark@simark.ca \
/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