From: Yao Qi <qiyaoltc@gmail.com>
To: Alan Hayward <alan.hayward@arm.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/8] AARCH64 SVE: Increse max register sizes
Date: Tue, 13 Dec 2016 11:48:00 -0000 [thread overview]
Message-ID: <20161213114742.GF25542@E107787-LIN> (raw)
In-Reply-To: <D4757157.1649A%alan.hayward@arm.com>
On 16-12-13 10:05:49, Alan Hayward wrote:
> Iâve just noticed I forgot to add a changelog for all of my patches.
> Apologies - Iâll add them for any V2 versions (or happy to repost all of
> them again with changelogs if required).
ChangeLog is not needed for V1.
>
> On 12/12/2016 18:10, "Yao Qi" <qiyaoltc@gmail.com> wrote:
>
> >On 16-12-05 12:26:24, Alan Hayward wrote:
> >> This is part of a series adding AARCH64 SVE support to gdb and
> >>gdbserver.
> >>
> >> In SVE the maximum size of a variable-length vector register is 256
> >>bytes,
> >> four
> >> times the current maximum size currently supported in gdb. This patch
> >> increases
> >> the max register size and max gdbserver buffer size accordingly.
> >
> >Joel expressed the willingness that we should make MAX_REGISTER_SIZE
> >gdbarch specific last time when it was changed from 32 to 64.
> >https://sourceware.org/ml/gdb-patches/2010-09/msg00245.html
> >I think we should make MAX_REGISTER_SIZE gdbarch specific, or stop
> >using it at all.
>
> Iâm happy to do this if thatâs what people want. I avoided doing it
> because I
> didnât want to subtly break something and itâs going to be quite a large
> change -
> I might submit it a set of patches by itself.
>
You can start from changing amd64-tdep.c and frame.c, which are
interesting to most of people here. It shouldn't take long to finish
the patch, and post it to get feedback quickly. If people agree/like
the change, then you can move on changing the rest in the same way.
--
Yao (é½å°§)
next prev parent reply other threads:[~2016-12-13 11:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 12:26 Alan Hayward
2016-12-12 18:11 ` Yao Qi
2016-12-13 10:05 ` Alan Hayward
2016-12-13 11:48 ` Yao Qi [this message]
2016-12-13 11:53 ` Joel Brobecker
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=20161213114742.GF25542@E107787-LIN \
--to=qiyaoltc@gmail.com \
--cc=alan.hayward@arm.com \
--cc=gdb-patches@sourceware.org \
/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