Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/commit] undefined regcache_set_valid_p in remote-mips.c
Date: Mon, 16 Mar 2009 22:52:00 -0000	[thread overview]
Message-ID: <20090316222156.GD384@adacore.com> (raw)
In-Reply-To: <200903162119.18075.pedro@codesourcery.com>

> Ah, I knew I had been there before:
> 
>  http://sourceware.org/ml/gdb-patches/2008-08/msg00475.html

FWIW, I wonder what's best in this case:
  (1) Leave the code as is, fearing that we might break something,
      but with a strong suspicion that it is broken by an earlier change;
  (2) Try fixing it blindly using visual code inspection for testing.

Short of being able to test the change ourselves, if you think as I do
that the target is very likely broken already, our best is all we have
to try to fix it.

The alternative is to make a call for help from people who care about
this target, and see if anyone is willing to help, at least with
the testing and integration.  Otherwise, we could consider deprecating
this target. It's always a shame to lose a target, but what can we do
if no one if we don't have the means to keep it alive?

-- 
Joel


      reply	other threads:[~2009-03-16 22:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-16 20:07 Joel Brobecker
2009-03-16 20:09 ` Daniel Jacobowitz
2009-03-16 20:20 ` Pedro Alves
2009-03-16 21:19 ` Joel Brobecker
2009-03-16 21:44   ` Pedro Alves
2009-03-16 22:52     ` 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=20090316222156.GD384@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