From: Indu Bhagat <indu.bhagat@oracle.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH, V4 09/14] opcodes: i386: new marker for insns that implicitly update stack pointer
Date: Sat, 6 Jan 2024 02:08:02 -0800 [thread overview]
Message-ID: <ffce5378-ee47-4508-ba9b-77cb2d4e4390@oracle.com> (raw)
In-Reply-To: <f82dcae2-1ec2-42ec-b5bc-a86d89332f9d@suse.com>
On 1/5/24 06:05, Jan Beulich wrote:
> On 03.01.2024 08:43, Indu Bhagat wrote:
>> --- a/opcodes/i386-opc.h
>> +++ b/opcodes/i386-opc.h
>> @@ -750,6 +750,9 @@ enum
>> /* No CSPAZO flags update indication. */
>> NF,
>>
>> + /* Instruction updates stack pointer implicitly. */
>> + ImplicitStackOp,
>> +
>> /* The last bitfield in i386_opcode_modifier. */
>> Opcode_Modifier_Num
>> };
>> @@ -796,6 +799,7 @@ typedef struct i386_opcode_modifier
>> unsigned int isa64:2;
>> unsigned int noegpr:1;
>> unsigned int nf:1;
>> + unsigned int implicitstackop:1;
>> } i386_opcode_modifier;
>
> I'm not happy to see a new attribute be introduced for this (a new
> OperandConstraint enumerator would seem more appropriate), while at
> the same time I can see that the Rex2 attribute used in two of the
> affected insns presently makes this impossible. However, with no
> other way out, I'd rather see Rex2 become a standalone attribute,
> and this one be another operand constraint.
>
To be sure I understand clearly, the ask here is to:
- Use unsigned int rex2:1 in struct i386_opcode_modifier instead
- Add a new OperandConstraint=IMPLICIT_STACK_OP
- Remove the OperandConstraint=REX2_REQUIRED
Is this right ?
Indu
next prev parent reply other threads:[~2024-01-06 10:08 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 7:15 [PATCH,V4 00/14] Synthesize CFI for hand-written asm Indu Bhagat
2024-01-03 7:15 ` [PATCH,V4 01/14] gas: dw2gencfi: minor rejig for cfi_sections_set and all_cfi_sections Indu Bhagat
2024-01-03 7:15 ` [PATCH,V4 02/14] gas: dw2gencfi: use all_cfi_sections instead of cfi_sections Indu Bhagat
2024-01-03 7:15 ` [PATCH,V4 03/14] gas: dw2gencfi: expose a new cfi_set_last_fde API Indu Bhagat
2024-01-03 7:15 ` [PATCH,V4 04/14] gas: dw2gencfi: move some tc_* defines to the header file Indu Bhagat
2024-01-03 7:15 ` [PATCH,V4 05/14] gas: dw2gencfi: expose dot_cfi_sections for scfidw2gen Indu Bhagat
2024-01-03 7:15 ` [PATCH,V4 06/14] gas: dw2gencfi: externalize the all_cfi_sections Indu Bhagat
2024-01-03 7:15 ` [PATCH,V4 07/14] gas: add new command line option --scfi[=all,none] Indu Bhagat
2024-01-03 7:15 ` [PATCH,V4 08/14] gas: scfidw2gen: new functionality to prepare for SCFI Indu Bhagat
2024-01-03 7:15 ` [PATCH,V4 09/14] opcodes: i386: new marker for insns that implicitly update stack pointer Indu Bhagat
2024-01-03 7:15 ` [PATCH,V4 10/14] gas: synthesize CFI for hand-written asm Indu Bhagat
2024-01-05 13:58 ` Jan Beulich
2024-01-08 0:46 ` Indu Bhagat
2024-01-08 8:16 ` Jan Beulich
2024-01-08 8:33 ` Indu Bhagat
2024-01-08 19:33 ` Indu Bhagat
2024-01-09 9:30 ` Jan Beulich
2024-01-10 6:10 ` Indu Bhagat
2024-01-10 9:44 ` Jan Beulich
2024-01-10 11:26 ` Indu Bhagat
2024-01-10 14:15 ` Jan Beulich
2024-01-10 19:43 ` Indu Bhagat
2024-01-11 8:13 ` Jan Beulich
2024-01-11 18:14 ` Indu Bhagat
2024-01-17 1:20 ` Indu Bhagat
2024-01-17 8:09 ` Jan Beulich
2024-01-03 7:15 ` [PATCH,V4 11/14] gas: doc: update documentation for the new listing option Indu Bhagat
2024-01-03 7:15 ` [PATCH,V4 12/14] i386-reg.tbl: Add a comment to reflect dependency on ordering Indu Bhagat
2024-01-03 7:15 ` [PATCH,V4 13/14] gas: testsuite: add a x86_64 testsuite for SCFI Indu Bhagat
2024-01-05 14:22 ` Jan Beulich
2024-01-05 22:29 ` Indu Bhagat
2024-01-08 8:11 ` Jan Beulich
2024-01-03 7:15 ` [PATCH,V4 14/14] gas/NEWS: announce the new SCFI command line option Indu Bhagat
2024-01-03 7:43 ` [PATCH,V4 09/14] opcodes: i386: new marker for insns that implicitly update stack pointer Indu Bhagat
2024-01-05 14:05 ` [PATCH, V4 " Jan Beulich
2024-01-06 10:08 ` Indu Bhagat [this message]
2024-01-08 8:12 ` 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=ffce5378-ee47-4508-ba9b-77cb2d4e4390@oracle.com \
--to=indu.bhagat@oracle.com \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.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).