Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Chen Gang <gang.chen.5i5j@gmail.com>
Cc: Andreas Schwab <schwab@suse.de>, gdb-patches@sourceware.org
Subject: Re: [PATCH v4] gdb/hppa-tdep.c: Fix logical working flow issues and check additional store instructions
Date: Mon, 15 Dec 2014 12:49:00 -0000	[thread overview]
Message-ID: <20141215124918.GV5457@adacore.com> (raw)
In-Reply-To: <548E65B5.7040606@gmail.com>

> Excuse me, I have no related test environments for parisc either. Maybe
> I can try to construct the related virtual environments for it, but I am
> still not quite sure whether it is enough.
> 
> Can we change to another way for it:
> 
>  - try to keep the original code no touch.
> 
>  - only fix the related typo issues according to the related documents,
>    do not add new features (e.g. do not check stby, stbdy, stwa, stda,
>    only give the related comments for them).
> 
>  - let it pass compiling.
> 
> Or, can we find related members in our gdb mailing list which has parisc
> environments?

I think finding people who can test your change would be ideal,
but is not required. I was just making it clear what my review
could bring, or rather not bring. I think it's fine to increase
the scope of the routine as you've been doing, as I think the risk
of disturbing currently supported instructions is small.

I am curious - and you do not have to reply if you do not want to -,
how did you get involved in this change? If you have no testing
environment, it probably means you're not using the code.  What
made you decide to try to fix it?

-- 
Joel


  reply	other threads:[~2014-12-15 12:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-14 13:36 Chen Gang
2014-12-14 19:35 ` Joel Brobecker
2014-12-15  4:31   ` Chen Gang
2014-12-15 12:49     ` Joel Brobecker [this message]
2014-12-15 14:24       ` Chen Gang

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=20141215124918.GV5457@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gang.chen.5i5j@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=schwab@suse.de \
    /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