From: Yao Qi <qiyaoltc@gmail.com>
To: Alan Hayward <Alan.Hayward@arm.com>
Cc: Pedro Alves <palves@redhat.com>,
"gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>,
Subject: Re: [PATCH 7/11] Add BFIN_MAX_REGISTER_SIZE
Date: Fri, 07 Apr 2017 16:04:00 -0000 [thread overview]
Message-ID: <861st4jjaq.fsf@gmail.com> (raw)
In-Reply-To: <F89A4E9B-0904-4C23-AA09-C51D1578C981@arm.com> (Alan Hayward's message of "Wed, 5 Apr 2017 15:51:40 +0000")
Alan Hayward <Alan.Hayward@arm.com> writes:
> There is some existing code in regcache.c that checks that no register in the
> target descriptor is greater than MAX_REGISTER_SIZE.
> Obviously, this code will vanish when MAX_REGISTER_SIZE disappears.
>
> If people think that this is an important check to have, then maybe there needs
> to be an additional patch set. For each target with a FOO_MAX_REGISTER_SIZE,
> in the init code for that target add:
> gdb_assert (FOO_MAX_REGISTER_SIZE >= max_register_size (gdbarch));
> ?
It is not just about checking. What if the assert fail?
FOO_MAX_REGISTER_SIZE is a strong claim for arch FOO. That is why I
suggested "or we can define ASTAT_REGISTER_SIZE".
>
> (To keep this simple I’d do it after adding these patches which add
> FOO_MAX_REGISTER_SIZE).
--
Yao (齐尧)
next prev parent reply other threads:[~2017-04-07 16:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 10:14 Alan Hayward
[not found] ` <86tw63p2rx.fsf@gmail.com>
[not found] ` <EDE97F7B-EFCE-4B4D-B996-C458F1DC7E56@arm.com>
2017-04-05 13:50 ` Andreas Schwab
2017-04-05 13:57 ` Alan Hayward
[not found] ` <86d1croshn.fsf@gmail.com>
2017-04-07 8:32 ` Alan Hayward
[not found] ` <3239de71-1e7c-22dd-172d-56a3baad292b@redhat.com>
2017-04-05 15:51 ` Alan Hayward
2017-04-07 16:04 ` Yao Qi [this message]
2017-04-07 16:22 ` Alan Hayward
2017-04-14 17:26 ` Mike Frysinger
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=861st4jjaq.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=Alan.Hayward@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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