public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Alan Modra <amodra@gmail.com>
To: Srinath Parvathaneni <srinath.parvathaneni@arm.com>
Cc: binutils@sourceware.org, nd@arm.com, richard.earnshaw@arm.com,
	Nick Clifton <nickc@redhat.com>
Subject: Re: [gas] arm: Add support for new unwinder directive ".pacspval".
Date: Wed, 16 Nov 2022 08:21:55 +1030	[thread overview]
Message-ID: <Y3QJ+xxqS3sXPVXm@squeak.grove.modra.org> (raw)
In-Reply-To: <59197c7d-b902-e036-d963-27fdd00033b0@redhat.com>

On Mon, Nov 14, 2022 at 02:20:43PM +0000, Nick Clifton via Binutils wrote:
> >          * testsuite/gas/arm/ehabi-pacbti-m.d: New test.
> >          * testsuite/gas/arm/ehabi-pacbti-m.s: Likewise.

New tests should be widely tested.  This on fails on arm-pe and other
non-ELF targets with complaints that .cfi directives are unknown.

	* testsuite/gas/arm/ehabi-pacbti-m.d: Limit test to ELF.

diff --git a/gas/testsuite/gas/arm/ehabi-pacbti-m.d b/gas/testsuite/gas/arm/ehabi-pacbti-m.d
index 6039945f931..1b13020835c 100644
--- a/gas/testsuite/gas/arm/ehabi-pacbti-m.d
+++ b/gas/testsuite/gas/arm/ehabi-pacbti-m.d
@@ -1,7 +1,8 @@
-# name: Unwind Stack Frame information for Armv8.1-M.Mainline PAC extension
-# source: ehabi-pacbti-m.s
-# as: -march=armv8.1-m.main+mve+pacbti
-# readelf: -u
+#name: Unwind Stack Frame information for Armv8.1-M.Mainline PAC extension
+#source: ehabi-pacbti-m.s
+#as: -march=armv8.1-m.main+mve+pacbti
+#readelf: -u
+#target: [is_elf_format]
 
 Unwind section '.ARM.exidx' at offset 0x5c contains 1 entry:
 

-- 
Alan Modra
Australia Development Lab, IBM

      reply	other threads:[~2022-11-15 21:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11 10:51 [PATCH][Binutils, gas] " Srinath Parvathaneni
2022-11-14 14:20 ` Nick Clifton
2022-11-15 21:51   ` Alan Modra [this message]

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=Y3QJ+xxqS3sXPVXm@squeak.grove.modra.org \
    --to=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=nd@arm.com \
    --cc=nickc@redhat.com \
    --cc=richard.earnshaw@arm.com \
    --cc=srinath.parvathaneni@arm.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).