public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Hafiz Abid Qadeer <abid_qadeer@mentor.com>
Cc: gdb-patches@sourceware.org, jiangshuai_li@c-sky.com
Subject: Re: [1/2] C-SKY Port
Date: Tue, 23 Oct 2018 16:42:00 -0000	[thread overview]
Message-ID: <9777cb488fab070bc4e1a05ce4b9fbed@simark.ca> (raw)
In-Reply-To: <c3cb40bd-8e0d-e339-2bb7-e014643272e4@mentor.com>

On 2018-10-23 08:48, Hafiz Abid Qadeer wrote:
>> A quick investigation shows it's because some raw registers are not in 
>> the
>> save reggroup.  So csky should probably be added to that big if in the 
>> test:
>> 
>> 	  if (bfd_arch == bfd_arch_frv || bfd_arch == bfd_arch_h8300
>> 	      || bfd_arch == bfd_arch_m32c || bfd_arch == bfd_arch_sh
>> 	      || bfd_arch == bfd_arch_alpha || bfd_arch == bfd_arch_v850
>> 	      || bfd_arch == bfd_arch_msp430 || bfd_arch == bfd_arch_mep
>> 	      || bfd_arch == bfd_arch_mips || bfd_arch == bfd_arch_v850_rh850
>> 	      || bfd_arch == bfd_arch_tic6x || bfd_arch == bfd_arch_mn10300
>> 	      || bfd_arch == bfd_arch_rl78 || bfd_arch == bfd_arch_score
>> 	      || bfd_arch == bfd_arch_riscv)
>> 	    {
>> 	      /* Raw registers.  If raw registers are not in save_reggroup,
>> 		 their status are unknown.  */
>> 	      if (gdbarch_register_reggroup_p (gdbarch, regnum, 
>> save_reggroup))
>> 		SELF_CHECK (status == REG_VALID);
>> 	      else
>> 		SELF_CHECK (status == REG_UNKNOWN);
>> 	    }
>> 	  else
>> 	    SELF_CHECK (status == REG_VALID);
>> 
> 
> When I was reviewing the test results for csky, I saw this fail in
> unittest.exp and fixed it by adding csky to the big if list as you
> mentioned above. Somehow I missed that patch when upstreaming the port.
> So if you are happy with that change then I will push it.

Yes please, consider it pre-approved.  We can take a look at removing 
the big list laster.

Thanks,

Simon

  reply	other threads:[~2018-10-23 16:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-25 10:43 [0/2] " Hafiz Abid Qadeer
2018-07-25 10:54 ` [1/2] " Hafiz Abid Qadeer
2018-07-27 15:49   ` Tom Tromey
2018-07-27 23:13     ` Hafiz Abid Qadeer
2018-08-08 10:53       ` Hafiz Abid Qadeer
2018-08-17  9:18       ` Abid, Hafiz
2018-08-24  9:15         ` Hafiz Abid Qadeer
2018-08-26  9:29       ` Joel Brobecker
2018-08-28 11:47         ` Hafiz Abid Qadeer
2018-10-21  2:55   ` Simon Marchi
2018-10-21  3:04     ` Hafiz Abid Qadeer
2018-10-21  3:22       ` Simon Marchi
2018-10-23 12:49         ` Hafiz Abid Qadeer
2018-10-23 16:42           ` Simon Marchi [this message]
2018-10-23 22:31             ` Hafiz Abid Qadeer
2018-07-25 10:55 ` [2/2] " Hafiz Abid Qadeer
2018-07-25 14:47   ` Eli Zaretskii

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=9777cb488fab070bc4e1a05ce4b9fbed@simark.ca \
    --to=simark@simark.ca \
    --cc=abid_qadeer@mentor.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jiangshuai_li@c-sky.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).