public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: New ARI warning Wed Sep 29 01:54:08 UTC 2010
Date: Thu, 30 Sep 2010 01:36:00 -0000	[thread overview]
Message-ID: <20100929185538.GO3007@adacore.com> (raw)
In-Reply-To: <201009291800.28269.pedro@codesourcery.com>

> The ARI suggestion makes no sense.  It's the ARI that needs fixing.

That's what I was thinking too.

> My guess is that the intention was to suggest replacing
> read_register() with regcache_read() at.al.  (that is, s/memory/register)
> read_register/write_register have been yanked out from the sources
> already few years ago.

That makes sense.

I have modified the ARI script accordingly, and rerun it, in order
to expunge the references to read_memory in the reference report.
The two extra emails we should get shortly from gdbadmin should reflect
these changes.

Thanks,
-- 
Joel

      reply	other threads:[~2010-09-29 18:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-29 13:34 GDB Administrator
2010-09-29 18:55 ` Joel Brobecker
2010-09-29 22:25   ` Pedro Alves
2010-09-30  1:36     ` Joel Brobecker [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=20100929185538.GO3007@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).