From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Document replacement for frame_register_read (deprecated).
Date: Tue, 23 Oct 2012 17:19:00 -0000 [thread overview]
Message-ID: <87objtf6mu.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1350941919-9862-1-git-send-email-brobecker@adacore.com> (Joel Brobecker's message of "Mon, 22 Oct 2012 17:38:39 -0400")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
Joel> This is inspired by a discussion from a long time ago:
Joel> http://www.sourceware.org/ml/gdb-patches/2011-03/msg01095.html
Joel> If you agree with the patch, we will also have to update the ARI
Joel> script to mention get_frame_register_value as the alternative.
Joel> And we might also want to rename the function as well. I don't think
Joel> we can rely on the ARI alone to avoid new uses of this function.
Joel> And once new uses are in, it's much harder to make sure we undo them.
Joel> Thoughts?
The patch seems reasonable to me.
Renaming seems like a decent idea, since there is a use in jit.c, which
was added long after this was deprecated.
I count 22 mentions (including the declaration) of frame_register_read
in the tree right now. Getting rid of all of them doesn't seem so
difficult, aside from the testing. This would be clearly better...
At least one of the current uses seems suspicious since it ignores the
result. I assume I'm missing some context though.
Tom
next prev parent reply other threads:[~2012-10-23 17:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 21:38 Joel Brobecker
2012-10-23 17:19 ` Tom Tromey [this message]
2012-11-09 0:10 ` Pedro Alves
2012-11-12 21:32 ` Joel Brobecker
2012-11-12 22:01 ` Joel Brobecker
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=87objtf6mu.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.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