From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simon.marchi@ericsson.com>
Cc: GDB Administrator <gdbadmin@sourceware.org>,
<gdb-patches@sourceware.org>
Subject: Re: New ARI warning Wed Aug 29 01:57:16 UTC 2018
Date: Wed, 29 Aug 2018 16:26:00 -0000 [thread overview]
Message-ID: <87r2ih3zt4.fsf@tromey.com> (raw)
In-Reply-To: <4602ce95-8f1b-2064-61ca-c0b027d2b21b@ericsson.com> (Simon Marchi's message of "Wed, 29 Aug 2018 10:33:47 -0400")
>>>>> "Simon" == Simon Marchi <simon.marchi@ericsson.com> writes:
Simon> I am not sure about this one. At first, I thought it was just a name clash,
Simon> the test looking for the "read_pc" function and wrongfully finding this line.
Simon> However, the check does purposefully look for "set_gdbarch_read_pc":
[...]
Simon> Is this gdbarch method really deprecated?
I don't know but I see other callers in-tree, which seems a bit peculiar.
Another unfinished deprecation I guess. Maybe we should be filing bugs
for these.
Tom
prev parent reply other threads:[~2018-08-29 16:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 1:57 GDB Administrator
2018-08-29 14:27 ` Simon Marchi
2018-08-29 14:34 ` Simon Marchi
2018-08-29 16:26 ` 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=87r2ih3zt4.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=gdbadmin@sourceware.org \
--cc=simon.marchi@ericsson.com \
/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