public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: Thomas Preudhomme <thomas.preudhomme@foss.arm.com>,
	Richard Earnshaw <richard.earnshaw@arm.com>,
	Alan Modra <amodra@gmail.com>,
	"binutils@sourceware.org" <binutils@sourceware.org>,
	Tristan Gingold <gingold@adacore.com>
Subject: Re: [PATCH, GAS] No IT usage deprecation for ARMv8-M
Date: Tue, 16 Jan 2018 11:22:00 -0000	[thread overview]
Message-ID: <4a57d7d0-79a2-d6a3-0d5a-9c271073f551@redhat.com> (raw)
In-Reply-To: <65ca534d-ee33-b40b-5b20-42d83a2a66a2@foss.arm.com>

Hi Thomas,

>     2018-01-15  Thomas Preud'homme  <thomas.preudhomme@arm.com>
> 
>     gas/
>         * config/tc-arm.c (it_fsm_post_encode): Do not warn if targeting M
>         profile architecture or if in autodetection mode.  Clarify that
>         deprecation is for performance reason and concerns Armv8-A and Armv8-R.
>         * testsuite/gas/arm/armv8-ar-bad.l: Adapt to new IT deprecation warning
>         message.
>         * testsuite/gas/arm/armv8-ar-it-bad.l: Likewise.
>         * testsuite/gas/arm/sp-pc-validations-bad-t-v8a.l: Likewise.
>         * testsuite/gas/arm/udf.l: Likewise.
>         * testsuite/gas/arm/udf.d: Assemble for Armv8-A explicitely.

> @Nick: is this fix ok for Binutils 2.30? 

Patch approved for the branch.

Cheers
  Nick


      parent reply	other threads:[~2018-01-16 11:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-01 14:40 Thomas Preudhomme
2017-12-01 14:42 ` [PATCH, GAS] Enable conditional Armv8-M instructions Thomas Preudhomme
2017-12-01 14:50   ` [PATCH, GAS] Add new macro for Thumb-only opcodes Thomas Preudhomme
2017-12-18 13:37     ` Nick Clifton
2017-12-18 13:36   ` [PATCH, GAS] Enable conditional Armv8-M instructions Nick Clifton
2017-12-18 13:35 ` [PATCH, GAS] No IT usage deprecation for ARMv8-M Nick Clifton
2018-01-15 14:25   ` Thomas Preudhomme
2018-01-15 14:41     ` Thomas Preudhomme
2018-01-16 11:22     ` Nick Clifton [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=4a57d7d0-79a2-d6a3-0d5a-9c271073f551@redhat.com \
    --to=nickc@redhat.com \
    --cc=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=gingold@adacore.com \
    --cc=richard.earnshaw@arm.com \
    --cc=thomas.preudhomme@foss.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).