public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Indu Bhagat <indu.bhagat@oracle.com>
To: binutils@sourceware.org
Cc: Indu Bhagat <indu.bhagat@oracle.com>
Subject: [PATCH 0/6] SFrame: support for .cfi_negate_ra_state in aarch64
Date: Wed, 14 Dec 2022 11:58:53 -0800	[thread overview]
Message-ID: <20221214195859.1233809-1-indu.bhagat@oracle.com> (raw)

Hello,

This patchset adds support for handling .cfi_negate_ra_state assembler
directive for SFrame information generation on aarch64. Without this support,
the .cfi_negate_ra_state directive was being ignored: no SFrame unwind
information was being generated for those code regions (bounded by the
.cfi_startproc/.cfi_endproc) that contained a .cfi_negate_ra_state directive.

The support is split in small patches to hopefully ease the review.

In a follow up patch series, support for .cfi_b_key_frame will be added.

Testing notes:
- Regression tested cross build of several targets on an x86_64 host and an
aarch64 host using a regression script that checks for failures in gas, ld,
binutils, libctf and libsframe.
- Regression tested native builds on x86_64 and aarch64.
- binutils/gdb try bot showed no new regressions.

Thanks,

Indu Bhagat (6):
  [1/6] sframe.h: add support for .cfi_negate_ra_state
  [2/6] gas: sframe: add support for .cfi_negate_ra_state
  [3/6] gas: sframe: testsuite: add testcase for .cfi_negate_ra_state
  [4/6] libsframe: provide new access API for mangled RA bit
  [5/6] objdump/readelf: sframe: emit marker for FREs with mangled RA
  [6/6] sframe: doc: update spec for the mangled-RA bit in FRE

 gas/gen-sframe.c                              | 41 +++++++++++++++----
 gas/gen-sframe.h                              |  6 ++-
 .../gas/cfi-sframe/cfi-sframe-aarch64-2.d     | 20 +++++++++
 ...ommon-empty-4.s => cfi-sframe-aarch64-2.s} |  3 +-
 gas/testsuite/gas/cfi-sframe/cfi-sframe.exp   |  2 +-
 gas/testsuite/gas/cfi-sframe/common-empty-4.d | 14 -------
 include/sframe-api.h                          |  7 ++++
 include/sframe.h                              | 23 +++++++----
 libsframe/doc/sframe-spec.texi                |  4 +-
 libsframe/sframe-dump.c                       | 13 ++++--
 libsframe/sframe.c                            | 18 ++++++++
 11 files changed, 113 insertions(+), 38 deletions(-)
 create mode 100644 gas/testsuite/gas/cfi-sframe/cfi-sframe-aarch64-2.d
 rename gas/testsuite/gas/cfi-sframe/{common-empty-4.s => cfi-sframe-aarch64-2.s} (85%)
 delete mode 100644 gas/testsuite/gas/cfi-sframe/common-empty-4.d

-- 
2.37.2


             reply	other threads:[~2022-12-14 19:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-14 19:58 Indu Bhagat [this message]
2022-12-14 19:58 ` [PATCH 1/6] [1/6] sframe.h: add support for .cfi_negate_ra_state Indu Bhagat
2022-12-14 19:58 ` [PATCH 2/6] [2/6] gas: sframe: " Indu Bhagat
2022-12-14 19:58 ` [PATCH 3/6] [3/6] gas: sframe: testsuite: add testcase " Indu Bhagat
2022-12-14 19:58 ` [PATCH 4/6] [4/6] libsframe: provide new access API for mangled RA bit Indu Bhagat
2022-12-14 19:58 ` [PATCH 5/6] [5/6] objdump/readelf: sframe: emit marker for FREs with mangled RA Indu Bhagat
2022-12-14 19:58 ` [PATCH 6/6] [6/6] sframe: doc: update spec for the mangled-RA bit in FRE Indu Bhagat
2022-12-16 16:39 ` [PATCH 0/6] SFrame: support for .cfi_negate_ra_state in aarch64 Nick Clifton

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=20221214195859.1233809-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).