From: "Kong, Lingling" <lingling.kong@intel.com>
To: "Beulich, Jan" <JBeulich@suse.com>,
Indu Bhagat <indu.bhagat@oracle.com>,
"Cui, Lili" <lili.cui@intel.com>, "H.J. Lu" <hjl.tools@gmail.com>,
"Hu, Lin1" <lin1.hu@intel.com>
Cc: "binutils@sourceware.org" <binutils@sourceware.org>
Subject: RE: [PATCH] opcodes: i386: fix dw2_regnum data type in reg_entry
Date: Thu, 11 Jan 2024 01:35:16 +0000 [thread overview]
Message-ID: <DM4PR11MB548765624B7816E24BE9DCB4EC682@DM4PR11MB5487.namprd11.prod.outlook.com> (raw)
In-Reply-To: <1cf65034-171c-44e7-bb7d-022f35451cb0@suse.com>
> -----Original Message-----
> From: Jan Beulich <jbeulich@suse.com>
> Sent: Tuesday, January 9, 2024 4:25 PM
> To: Indu Bhagat <indu.bhagat@oracle.com>; Cui, Lili <lili.cui@intel.com>; H.J. Lu
> <hjl.tools@gmail.com>; Kong, Lingling <lingling.kong@intel.com>; Hu, Lin1
> <lin1.hu@intel.com>
> Cc: binutils@sourceware.org
> Subject: Re: [PATCH] opcodes: i386: fix dw2_regnum data type in reg_entry
>
> On 09.01.2024 02:12, Indu Bhagat wrote:
> > The DWARF register numbers for the APX EGRPs start with 130. The data
> > type holding the same currently is signed char.
> >
> > ChangeLog:
> > * opcodes/i386-opc.h (reg_entry): Bump to signed short.
>
> So yes, something needs doing. But there are further questions to be raised to the
> original authors: Was the code tested at all in this regard? Why do numbers start
> at 130, when according to i386-reg.tbl
> 128 and 129 are unused (and would hence be more natural to [also] use)?
>
Hi,
This is because for some historical reasons, some numbers(126-129) have been agreed to be reserved.
Details can be found in https://groups.google.com/g/x86-64-abi/c/GS8LZf5nQFk.
Thanks!
Lingling
-> > --- a/opcodes/i386-opc.h
> > +++ b/opcodes/i386-opc.h
> > @@ -1047,7 +1047,7 @@ typedef struct
> > #define RegIZ (RegIP - 1)
> > /* FLAT is a fake segment register (Intel mode). */
> > #define RegFlat ((unsigned char) ~0)
> > - signed char dw2_regnum[2];
> > + signed short dw2_regnum[2];
> > #define Dw2Inval (-1)
> > }
> > reg_entry;
>
> It's a little sad that non-64-bit field also has its size increased.
> Right now either way the structure size as a whole is the same, but down the
> road this may end up a little wasteful.
>
> Jan
next prev parent reply other threads:[~2024-01-11 1:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 1:12 Indu Bhagat
2024-01-09 1:12 ` [PATCH] opcodes: gas: i386: use Rex2 as attribute not constraint Indu Bhagat
2024-01-09 8:14 ` Jan Beulich
2024-01-09 8:24 ` [PATCH] opcodes: i386: fix dw2_regnum data type in reg_entry Jan Beulich
2024-01-11 1:35 ` Kong, Lingling [this message]
2024-01-11 7:43 ` Jan Beulich
2024-01-11 7:59 ` Kong, Lingling
2024-01-11 8:05 ` Jan Beulich
2024-01-11 13:27 ` H.J. Lu
2024-01-11 14:05 ` Jan Beulich
2024-01-20 0:45 ` Indu Bhagat
2024-01-22 7:49 ` Jan Beulich
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=DM4PR11MB548765624B7816E24BE9DCB4EC682@DM4PR11MB5487.namprd11.prod.outlook.com \
--to=lingling.kong@intel.com \
--cc=JBeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=indu.bhagat@oracle.com \
--cc=lili.cui@intel.com \
--cc=lin1.hu@intel.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).