public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: Indu Bhagat <indu.bhagat@oracle.com>, binutils@sourceware.org
Subject: Re: [PATCH 0/5] SFrame: add support for .cfi_b_key_frame
Date: Mon, 19 Dec 2022 15:36:40 +0000	[thread overview]
Message-ID: <e5fca105-80f0-dfd5-c5ef-e71530b6ac0a@redhat.com> (raw)
In-Reply-To: <20221214200756.1234528-1-indu.bhagat@oracle.com>

Hi Indu,

> - 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.

With this patch series applied on top of today's (19 dec) sources I see one
new failure in the gas testsuite for a toolchain configured as aarch64-linux-gnu:

   regexp_diff match failure
   regexp "^    Num FREs: 4$"
   line   "    Num FREs: 6"
   regexp_diff match failure
   regexp "^    0+0008 +sp\+16 +c-16 +c-8\[s\] +$"
   line   "    0000000000000004  sp+0      u         u[s]         "
   regexp_diff match failure
   regexp "^    func idx \[1\]: pc = 0x0, size = 20 bytes, pauth = B key$"
   line   "    0000000000000008  sp+16     c-16      c-8[s]       "
   regexp_diff match failure
   regexp "^    STARTPC + CFA + FP +  RA +$"
   line   "    func idx [1]: pc = 0x0, size = 20 bytes, pauth = B key"
   regexp_diff match failure
   regexp "^    0+0000 +sp\+0 +u +u +$"
   line   "    STARTPC         CFA       FP        RA           "
   regexp_diff match failure
   regexp "^    0+0008 +sp\+16 +c-16 +c-8\[s\] +$"
   line   "    0000000000000000  sp+0      u         u            "
   FAIL: SFrame cfi_b_key_frame and cfi_negate_ra_state composite test

Possibly this is because another patch needs to be applied first ?  Please could
you check and let me know.

Cheers
   Nick


  parent reply	other threads:[~2022-12-19 15:36 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-14 20:07 Indu Bhagat
2022-12-14 20:07 ` [PATCH 1/5] [1/5] sframe.h: " Indu Bhagat
2022-12-14 20:07 ` [PATCH 2/5] [2/5] gas: sframe: " Indu Bhagat
2022-12-14 20:07 ` [PATCH 3/5] [3/5] objdump/readelf: sframe: emit marker for SFrame FDE with B key Indu Bhagat
2022-12-14 20:07 ` [PATCH 4/5] [4/5] gas: sframe: testsuite: add testcase for .cfi_b_key_frame Indu Bhagat
2022-12-14 20:07 ` [PATCH 5/5] [5/5] sframe: doc: update documentation for pauth key in SFrame FDE Indu Bhagat
2022-12-19 15:36 ` Nick Clifton [this message]
2022-12-19 17:27   ` [PATCH 0/5] SFrame: add support for .cfi_b_key_frame Indu Bhagat
2022-12-19 20:23   ` [COMMITTED, V2 " Indu Bhagat
2022-12-19 20:23     ` [COMMITTED, V2 1/5] [1/5] sframe.h: " Indu Bhagat
2022-12-19 20:23     ` [COMMITTED, V2 2/5] [2/5] gas: sframe: " Indu Bhagat
2022-12-19 20:23     ` [COMMITTED, V2 3/5] [3/5] objdump/readelf: sframe: emit marker for SFrame FDE with B key Indu Bhagat
2022-12-19 20:23     ` [COMMITTED, V2 4/5] [4/5] gas: sframe: testsuite: add testcase for .cfi_b_key_frame Indu Bhagat
2022-12-19 20:23     ` [COMMITTED, V2 5/5] [5/5] sframe: doc: update documentation for pauth key in SFrame FDE Indu Bhagat
2022-12-19 21:11     ` [COMMITTED, V2 0/5] SFrame: add support for .cfi_b_key_frame Indu Bhagat
2022-12-19 21:14   ` [PATCH, " Indu Bhagat
2022-12-19 21:14     ` [PATCH, V2 1/5] [1/5] sframe.h: " Indu Bhagat
2022-12-19 21:14     ` [PATCH, V2 2/5] [2/5] gas: sframe: " Indu Bhagat
2022-12-19 21:14     ` [PATCH, V2 3/5] [3/5] objdump/readelf: sframe: emit marker for SFrame FDE with B key Indu Bhagat
2022-12-19 21:14     ` [PATCH, V2 4/5] [4/5] gas: sframe: testsuite: add testcase for .cfi_b_key_frame Indu Bhagat
2022-12-19 21:14     ` [PATCH, V2 5/5] [5/5] sframe: doc: update documentation for pauth key in SFrame FDE Indu Bhagat
2022-12-21 18:19     ` [PATCH, V2 0/5] SFrame: add support for .cfi_b_key_frame Indu Bhagat
2022-12-22  8:40       ` 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=e5fca105-80f0-dfd5-c5ef-e71530b6ac0a@redhat.com \
    --to=nickc@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=indu.bhagat@oracle.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).