From: Indu Bhagat <indu.bhagat@oracle.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH,V4 10/14] gas: synthesize CFI for hand-written asm
Date: Tue, 16 Jan 2024 17:20:14 -0800 [thread overview]
Message-ID: <962e43b8-5eea-4f71-9d36-4f95af6a043c@oracle.com> (raw)
In-Reply-To: <20b71f7f-7c8b-41fd-a85c-6887cc19e5ff@suse.com>
On 1/10/24 01:44, Jan Beulich wrote:
> On 10.01.2024 07:10, Indu Bhagat wrote:
>> On 1/9/24 01:30, Jan Beulich wrote:
>>> On 08.01.2024 20:33, Indu Bhagat wrote:
>>>> On 1/5/24 05:58, Jan Beulich wrote:
>>>>> On 03.01.2024 08:15, Indu Bhagat wrote:
>>>>>> +/* Check whether a '66H' prefix accompanies the instruction.
>>>>> With APX 16-bit operand size isn't necessarily represented by a 66h
>>>>> prefix, but perhaps with an "embedded prefix" inside the EVEX one.
>>>>> Therefore both the comment and even more so ...
>>>>>
>>>>>> + The current users of this API are in the handlers for PUSH, POP
>>>>>> + instructions. These instructions affect the stack pointer implicitly: the
>>>>>> + operand size (16, 32, or 64 bits) determines the amount by which the stack
>>>>>> + pointer is decremented (2, 4 or 8). When '66H' prefix is present, the
>>>>>> + instruction has a 16-bit operand. */
>>>>>> +
>>>>>> +static bool
>>>>>> +ginsn_prefix_66H_p (i386_insn insn)
>>>>> ... the function name would better not allude to just the legacy
>>>>> encoding. Maybe ginsn_opsize_prefix_p()?
>>>>>
>>>> Isnt 66H_p more readable and easier to follow because that's what the
>>>> function is currently checking ? If more scenarios were being handled,
>>>> ginsn_opsize_prefix_p () would fit better.
>>> Well, as said - with APX you can't get away with just 0x66 prefix checking.
>>> That prefix is simply illegal to use with EVEX-encoded insns.
>>>
>> I am using the following in ginsn_opsize_prefix_p ():
>>
>> !(i.prefix[REX_PREFIX] & REX_W) && i.prefix[DATA_PREFIX] == 0x66
> That addresses one half of my earlier remarks. Note however that elsewhere
> we never check i.prefix[DATA_PREFIX] against being 0x66; we only ever check
> for it being zero or non-zero. I'd like this to remain consistent.
>
> For EVEX-encoded APX insns this isn't going to be sufficient though. See
> respective code in process_suffix():
>
> /* The DATA PREFIX of EVEX promoted from legacy APX instructions
> needs to be adjusted. */
> if (i.tm.opcode_space == SPACE_EVEXMAP4)
> {
> gas_assert (!i.tm.opcode_modifier.opcodeprefix);
> i.tm.opcode_modifier.opcodeprefix = PREFIX_0X66;
> }
> else if (!add_prefix (prefix))
> return 0;
>
> So you'll need to also check for that combination, plus take care of
> avoiding insns where PREFIX_0X66 alters operation, not operand size
> (ADCX being an example).
[V5 is now committed. I am continuing to work on some of the discussed
pending items from V4.]
Thanks. So looks like to correctly check for prefix 66H, one needs to
check that:
- !(i.prefix[REX_PREFIX] & REX_W) && i.prefix[DATA_PREFIX]
- (i.tm.opcode_space == SPACE_EVEXMAP4
&& i.tm.opcode_modifier.opcodeprefix == PREFIX_0X66);
- selectively handle the specific ops where PREFIX_0x66 alters
operation. I tried looking around but haven't found a targetted way to
identify such ops. Is there a way ?
Alternatively, since x86_ginsn_new () will be called after
process_suffix (), I wonder if I can update the code to simply check for
i.suffix to be 'w' for reliably detecting the 16-bit ops for all x86
insns. Is the check on suffix correct and reliable ?
next prev parent reply other threads:[~2024-01-17 1:20 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 7:15 [PATCH,V4 00/14] Synthesize " 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 [this message]
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
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=962e43b8-5eea-4f71-9d36-4f95af6a043c@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).