From: Simon Marchi <simark@simark.ca>
To: Hafiz Abid Qadeer <abid_qadeer@mentor.com>, gdb-patches@sourceware.org
Cc: jiangshuai_li@c-sky.com
Subject: Re: [1/2] C-SKY Port
Date: Sun, 21 Oct 2018 03:22:00 -0000 [thread overview]
Message-ID: <1799f181-2531-dc53-4934-6f436a2b858c@simark.ca> (raw)
In-Reply-To: <bfecceb4-8845-a3de-c4dd-c83f4af0011f@mentor.com>
On 2018-10-20 11:04 p.m., Hafiz Abid Qadeer wrote:
> On 20/10/18 19:55, Simon Marchi wrote:
>> On 2018-07-25 6:54 a.m., Hafiz Abid Qadeer wrote:
>
>> Hi Hafiz,
>>
>> I noticed the "cooked_read" selftest fails with c-sky (ever since the c-sky support was added):
>>
>> (gdb) maintenance selftest cooked_read
>> Running selftest regcache::cooked_read_test.
>> ...
>> Self test failed: arch csky: self-test failed at /home/simark/src/binutils-gdb/gdb/regcache.c:1697
>> Self test failed: arch csky:ck510: self-test failed at /home/simark/src/binutils-gdb/gdb/regcache.c:1697
>> Self test failed: arch csky:ck610: self-test failed at /home/simark/src/binutils-gdb/gdb/regcache.c:1697
>> Self test failed: arch csky:ck801: self-test failed at /home/simark/src/binutils-gdb/gdb/regcache.c:1697
>> Self test failed: arch csky:ck802: self-test failed at /home/simark/src/binutils-gdb/gdb/regcache.c:1697
>> Self test failed: arch csky:ck803: self-test failed at /home/simark/src/binutils-gdb/gdb/regcache.c:1697
>> Self test failed: arch csky:ck807: self-test failed at /home/simark/src/binutils-gdb/gdb/regcache.c:1697
>> Self test failed: arch csky:ck810: self-test failed at /home/simark/src/binutils-gdb/gdb/regcache.c:1697
>> Self test failed: arch csky:any: self-test failed at /home/simark/src/binutils-gdb/gdb/regcache.c:1697
>> ...
>> Self test failed: self-test failed at /home/simark/src/binutils-gdb/gdb/selftest-arch.c:86
>> Ran 1 unit tests, 1 failed
>>
>> Could you take a look?
> Hi Simon,
> Thanks for letting me know. I am traveling at the moment. Will take a
> look at it when I am back in a few days.
Ok, thanks!
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);
But I'm tempted to replace all of that with simply;
/* 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);
We won't have to maintain this big list, and I don't think we lose any testing
coverage/safety. For architectures for which all raw registers are in the
save_reggroup (all arches not listed above), we will still always assert that
status == REG_VALID.
I'll let you take a look when you have time.
Simon
next prev parent reply other threads:[~2018-10-21 3:22 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 [this message]
2018-10-23 12:49 ` Hafiz Abid Qadeer
2018-10-23 16:42 ` Simon Marchi
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=1799f181-2531-dc53-4934-6f436a2b858c@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