From: Claudiu Zissulescu Ianculescu <claziss@gmail.com>
To: Shahab Vahedi <shahab.vahedi@gmail.com>, Nick Clifton <nickc@redhat.com>
Cc: Anton Kolesov <akolesov@synopsys.com>,
Binutils <binutils@sourceware.org>,
Shahab Vahedi <Shahab.Vahedi@synopsys.com>,
Claudiu Zissulescu <Claudiu.Zissulescu@synopsys.com>,
Francois Bedard <Francois.Bedard@synopsys.com>
Subject: Re: [PATCH] arc: Add support for ARC HS extra registers in core files
Date: Fri, 10 Apr 2020 14:56:24 +0300 [thread overview]
Message-ID: <CAL0iMy3wQrdAKe30+yNLqWKUPXeRAoymNrGmWxJLepaL+HV5uA@mail.gmail.com> (raw)
In-Reply-To: <20200406090643.GA1975@gmail.com>
Thank you for the clarification. It looks all right from my side.
Nick, am I allowed to push Shahab's patch? It does touches some generic files.
Thanks,
Claudiu
On Mon, Apr 6, 2020 at 12:06 PM Shahab Vahedi <shahab.vahedi@gmail.com> wrote:
>
> Hi Claudiu,
>
> > >
> > > Hi Shahab,
> > >
> > > I don't really like the ARC_V2 name. All ARC variants can have extra registers
> > > from r32 to r59 called extension core registers :) I would go for something more
> > > generic like ARC_EXT_REG, or something like that
> > >
>
> I have looked into this a little bit further:
>
> As Anton mentioned, since NT_ARC_V2 is entangled with kernel's ptrace, it is
> not a not a viable option to change it.
>
> Regarding the ".reg-arc-v2" section, there can be 3 registers in there: r30,
> r58, and r59. The r58/r59 pair are the accumulator registers. r30 is the tricky
> one. In ARCompact (ARC 600/700), r30 used to be called ILINK2 and was not a
> userspace register. In ARCv2, that has changed. It is considered a general
> purpose register, hence its inclusion in ".reg-arc-v2". I am afraid that the
> name of this note indeed reflects how tied it is to ARCv2.
>
>
> Cheers,
> Shahab
next prev parent reply other threads:[~2020-04-10 11:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 15:02 Shahab Vahedi
2020-03-31 9:29 ` Claudiu Zissulescu Ianculescu
2020-03-31 9:41 ` Anton Kolesov
2020-04-06 9:06 ` Shahab Vahedi
2020-04-10 11:56 ` Claudiu Zissulescu Ianculescu [this message]
2020-04-14 10:40 ` Nick Clifton
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=CAL0iMy3wQrdAKe30+yNLqWKUPXeRAoymNrGmWxJLepaL+HV5uA@mail.gmail.com \
--to=claziss@gmail.com \
--cc=Claudiu.Zissulescu@synopsys.com \
--cc=Francois.Bedard@synopsys.com \
--cc=Shahab.Vahedi@synopsys.com \
--cc=akolesov@synopsys.com \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.com \
--cc=shahab.vahedi@gmail.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).