From: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>
To: Kyrill Tkachov <kyrylo.tkachov@foss.arm.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Cc: Ramana Radhakrishnan <ramana.radhakrishnan@arm.com>,
Nick Clifton <nickc@redhat.com>
Subject: Re: [PATCH][ARM] Add deprecation warning on pre-v4t architecture revisions
Date: Fri, 08 Apr 2016 09:28:00 -0000 [thread overview]
Message-ID: <570779C0.30408@arm.com> (raw)
In-Reply-To: <56D5C086.4070802@foss.arm.com>
On 01/03/16 16:17, Kyrill Tkachov wrote:
> Hi all,
>
> For GCC 6 we want to deprecate architecture revisions prior to ARMv4T.
> This patch implements this by documenting the deprecation in invoke.texi
> and adding
> a warning whenever the user specifies an -march or -mcpu option that
> selects such
> an architecture revision.
>
> Bootstrapped and tested on arm.
>
> Ok for trunk?
>
> Thanks,
> Kyrill
>
> P.S. I'll add a note to changes.html to that effect separately.
>
> 2016-03-01 Kyrylo Tkachov <kyrylo.tkachov@arm.com>
>
> * config/arm/arm.c (arm_option_override): Warn on pre-ARMv4T
> architecture revisions.
> * doc/invoke.texi (ARM Options): Add note on deprecation of pre-ARMv4T
> architecture revisions.
>
> 2016-03-01 Kyrylo Tkachov <kyrylo.tkachov@arm.com>
>
> * gcc.target/arm/ftest-armv4-arm.c: Add dg-warning for deprecation
> warning.
> * gcc.target/arm/pr62554.c: Likewise.
> * gcc.target/arm/pr69610-1.c: Likewise.
> * gcc.target/arm/pr69610-2.c: Likewise.
OK
R.
next prev parent reply other threads:[~2016-04-08 9:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 16:17 Kyrill Tkachov
2016-03-07 15:40 ` Kyrill Tkachov
2016-03-23 10:24 ` Kyrill Tkachov
2016-03-31 13:12 ` Kyrill Tkachov
2016-04-07 13:48 ` Kyrill Tkachov
2016-04-08 9:28 ` Richard Earnshaw (lists) [this message]
2016-04-15 13:39 ` Kyrill Tkachov
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=570779C0.30408@arm.com \
--to=richard.earnshaw@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kyrylo.tkachov@foss.arm.com \
--cc=nickc@redhat.com \
--cc=ramana.radhakrishnan@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).