public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Indu Bhagat <indu.bhagat@oracle.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: binutils@sourceware.org, Nick Clifton <nickc@redhat.com>
Subject: Re: [PATCH,V4 10/14] gas: synthesize CFI for hand-written asm
Date: Mon, 8 Jan 2024 00:33:51 -0800	[thread overview]
Message-ID: <30fa8319-e6b3-4974-94e1-29c96e68310b@oracle.com> (raw)
In-Reply-To: <a46c1277-1ac3-4037-a4a6-c6b743997c83@suse.com>

On 1/8/24 00:16, Jan Beulich wrote:
> On 08.01.2024 01:46, Indu Bhagat wrote:
>> Hi Jan, Nick,
>>
>> I am working on addressing the review comments in V4 and will continue
>> that review in a separate thread.
>>
>> Meanwhile...
>>
>> On 1/5/24 05:58, Jan Beulich wrote:
>>>> +      dwarf_reg = ginsn_dw2_regnum (temp);
>>>> +    }
>>>> +
>>>> +  gas_assert (dwarf_reg != Dw2Inval); /* Needs to be addressed.  */
>>> Without actually addressing this (and possible similar cases elsewhere), I
>>> don't think this can go in as other than experimental code (which the
>>> NEWS entry then should state, and where there then should be a plan for an
>>> easy approach of probing gas for no-longer-experimental SCFI support).
>>
>> ... in this specific case, the /* Needs to be addressed.  */ comment is
>> somewhat stale and may have lead the impression that this is an
>> unhandled case (EIP is the pending unhandled case, I will deal with it
>> in V5).
>>
>> Moving forward, I would like to get consensus on whats the way forward
>> for SCFI series, especially whether there is agreement on releasing what
>> will be the V5 with binutils 2.42.
>>
>> My take on "SCFI should go as experimental code" : my priority is to get
>> this option to users and to continue development of SCFI incrementally
>> with the help/reviews from community.  If the reviewers/maintainers
>> think, offering this first as --scfi=experimental, which later is
>> established as --scfi=all, in a future release is the best way to move
>> forward, I can make the necessary changes now.
> 
> I'd be okay with this as a plan. Before fully supported, I'd actually hope
> to see at least one other architecture to also use this machinery. Yet
> maybe that's asking for too much ...
> 

Thanks Jan.

BTW, I have implementation for SCFI for aarch64 in a personal branch. 
FWIW, the current state of ginsn/scfi  machinery (as posted in V4) 
"works" on aarch64. That said, the aarch64 implementation is minimally 
tested at this time and needs more work.

I hope to upstream that at some point.

Indu


  reply	other threads:[~2024-01-08  8:34 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 [this message]
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
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=30fa8319-e6b3-4974-94e1-29c96e68310b@oracle.com \
    --to=indu.bhagat@oracle.com \
    --cc=binutils@sourceware.org \
    --cc=jbeulich@suse.com \
    --cc=nickc@redhat.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).