From: Indu Bhagat <indu.bhagat@oracle.com>
To: binutils@sourceware.org
Cc: Indu Bhagat <indu.bhagat@oracle.com>
Subject: [PATCH,V3 0/2] Testcase refactoring and fix PR gas/31284
Date: Fri, 26 Jan 2024 01:19:15 -0800 [thread overview]
Message-ID: <20240126091917.3266816-1-indu.bhagat@oracle.com> (raw)
Hi,
Sending V3 after addressing review comments on "PATCH 2/2 gas: scfi:
untraceable control flow should be a hard error".
I sent the first version of the series erroneously as V2.
https://sourceware.org/pipermail/binutils/2024-January/132085.html
Once approved, OK to apply to 2.42 as well ?
Thanks,
Indu Bhagat (2):
x86: testsuite: scfi: adjust COFI testcase
gas: scfi: untraceable control flow should be a hard error
gas/ginsn.c | 4 +-
gas/testsuite/gas/scfi/x86_64/ginsn-cofi-1.l | 38 +++++++++++++++++++
.../x86_64/{scfi-cofi-1.s => ginsn-cofi-1.s} | 4 --
gas/testsuite/gas/scfi/x86_64/scfi-cofi-1.d | 5 ---
gas/testsuite/gas/scfi/x86_64/scfi-cofi-1.l | 3 --
.../gas/scfi/x86_64/scfi-unsupported-cfg-1.l | 2 +-
gas/testsuite/gas/scfi/x86_64/scfi-x86-64.exp | 3 +-
7 files changed, 42 insertions(+), 17 deletions(-)
create mode 100644 gas/testsuite/gas/scfi/x86_64/ginsn-cofi-1.l
rename gas/testsuite/gas/scfi/x86_64/{scfi-cofi-1.s => ginsn-cofi-1.s} (84%)
delete mode 100644 gas/testsuite/gas/scfi/x86_64/scfi-cofi-1.d
delete mode 100644 gas/testsuite/gas/scfi/x86_64/scfi-cofi-1.l
--
2.43.0
next reply other threads:[~2024-01-26 9:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 9:19 Indu Bhagat [this message]
2024-01-26 9:19 ` [PATCH,V3 1/2] x86: testsuite: scfi: adjust COFI testcase Indu Bhagat
2024-01-26 9:19 ` [PATCH,V3 2/2] gas: scfi: untraceable control flow should be a hard error Indu Bhagat
2024-01-26 11:57 ` [PATCH,V3 0/2] Testcase refactoring and fix PR gas/31284 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=20240126091917.3266816-1-indu.bhagat@oracle.com \
--to=indu.bhagat@oracle.com \
--cc=binutils@sourceware.org \
/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).