From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] arm64: Fix fallout of asm/opcodes.h removal
Date: Tue, 6 Dec 2016 15:30:56 +0000 [thread overview]
Message-ID: <20161206153056.GN2498@arm.com> (raw)
In-Reply-To: <1481038065-32153-1-git-send-email-marc.zyngier@arm.com>
On Tue, Dec 06, 2016 at 03:27:42PM +0000, Marc Zyngier wrote:
> As part of the asm/opcodes.h removal, the SET_PSTATE_{PAN,UAO} macros
> have been switch to using the .inst directive instead of .long (as
> this has the advantage of providing a correct disassembly). This
> had the side effect of bringing back an ugly gas bug that shows up
> when .inst is used within alternative sequences.
>
> This series works around the problem by:
> - adding detection code for the broken binutils,
> - work around the issue by falling back to .long when using a buggy
> assembler.
>
> This has been tested with both binutils 2.25 (broken) and 2.27
> (fixed), with both LE and BE builds.
>
> Marc Zyngier (2):
> arm64: Add detection code for broken .inst support in binutils
> arm64: Work around broken .inst when defective gas is detected
For the two patches (not the bonus xen one!):
Acked-by: Will Deacon <will.deacon@arm.com>
Thanks for sticking with this...
Will
prev parent reply other threads:[~2016-12-06 15:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-06 15:27 [PATCH v2 0/2] arm64: Fix fallout of asm/opcodes.h removal Marc Zyngier
2016-12-06 15:27 ` [PATCH v2 1/2] arm64: Add detection code for broken .inst support in binutils Marc Zyngier
2016-12-06 15:27 ` [PATCH v2] arm/arm64: xen: Move shared architecture headers to include/xen/arm Marc Zyngier
2016-12-06 15:34 ` Marc Zyngier
2016-12-06 15:27 ` [PATCH v2 2/2] arm64: Work around broken .inst when defective gas is detected Marc Zyngier
2016-12-06 16:28 ` Dave Martin
2016-12-06 17:38 ` Dave Martin
2016-12-06 15:30 ` Will Deacon [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=20161206153056.GN2498@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.