From: Indu Bhagat <indu.bhagat@oracle.com>
To: Nick Clifton <nickc@redhat.com>, binutils@sourceware.org
Subject: Re: [PATCH, RFC 6/9] gas: dw2gencfi: ignore all .cfi_* directives with --scfi=all
Date: Fri, 29 Sep 2023 23:20:53 -0700 [thread overview]
Message-ID: <ed24d161-ba25-1bc4-23e9-c3be286edc49@oracle.com> (raw)
In-Reply-To: <5ca08037-f429-1ef1-adb1-a683a4fb40e6@redhat.com>
On 9/28/23 07:10, Nick Clifton wrote:
> Hi Indu,
>
>> @@ -806,6 +806,12 @@ dot_cfi (int arg)
>> offsetT offset;
>> unsigned reg1, reg2;
>> + if (flag_synth_cfi)
>> + {
>> + ignore_rest_of_line ();
>> + return;
>> + }
>> +
>
> I am concerned about this behaviour. I understand that mixing
> synthetic CFI statements and real ones would be a bad idea, but
> I think that silently ignoring the real ones is a mistake. At
> the very least you ought to generate a warning message letting
> the user know that their cfi instructions are being ignored.
>
Yes, we could trigger one warning per function, when we see, say a
.cfi_startproc, for a asm function for which user specified --scfi=all:
"Warning: --scfi=all ignores sythesizable CFI directives for function
'foo'"
That said, it looks like for --scfi=all, we will need to honor at least
the following from the user:
- .cfi_sections
- .cfi_label
- .cfi_signal_frame
Thanks
next prev parent reply other threads:[~2023-09-30 6:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 23:03 [PATCH,RFC 0/9] SCFI implementation in GNU assembler Indu Bhagat
2023-09-20 23:03 ` [PATCH,RFC 1/9] gas: dw2gencfi: minor rejig for cfi_sections_set and all_cfi_sections Indu Bhagat
2023-09-20 23:03 ` [PATCH,RFC 2/9] gas: dw2gencfi: use all_cfi_sections instead of cfi_sections Indu Bhagat
2023-09-20 23:03 ` [PATCH,RFC 3/9] gas: dw2gencfi: expose a new cfi_set_last_fde API Indu Bhagat
2023-09-20 23:03 ` [PATCH,RFC 4/9] gas: dw2gencfi: move some tc_* defines to the header file Indu Bhagat
2023-09-20 23:03 ` [PATCH,RFC 5/9] gas: add new command line option --scfi[=all,none] Indu Bhagat
2023-09-28 14:04 ` Nick Clifton
2023-09-30 6:13 ` Indu Bhagat
2023-09-20 23:03 ` [PATCH,RFC 6/9] gas: dw2gencfi: ignore all .cfi_* directives with --scfi=all Indu Bhagat
2023-09-28 14:10 ` [PATCH, RFC " Nick Clifton
2023-09-30 6:20 ` Indu Bhagat [this message]
2023-09-20 23:03 ` [PATCH,RFC 7/9] gas: scfidw2gen: new functionality to prepapre for SCFI Indu Bhagat
2023-09-20 23:04 ` [PATCH,RFC 8/9] gas: synthesize CFI for hand-written asm Indu Bhagat
2023-09-28 14:58 ` Nick Clifton
2023-09-30 6:43 ` Indu Bhagat
2023-09-20 23:04 ` [PATCH,RFC 9/9] gas: testsuite: add a x86_64 testsuite for SCFI Indu Bhagat
2023-09-28 15:01 ` [PATCH,RFC 0/9] SCFI implementation in GNU assembler Nick Clifton
2023-09-30 6:44 ` Indu Bhagat
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=ed24d161-ba25-1bc4-23e9-c3be286edc49@oracle.com \
--to=indu.bhagat@oracle.com \
--cc=binutils@sourceware.org \
--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).