public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Thomas Preudhomme <thomas.preudhomme@foss.arm.com>
To: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>,
	Kyrill Tkachov <kyrylo.tkachov@arm.com>,
	Ramana Radhakrishnan <ramana.radhakrishnan@arm.com>,
	"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, wwwdocs/ARM] Deprecate ARMv5 and ARMv5E support
Date: Thu, 16 Feb 2017 17:48:00 -0000	[thread overview]
Message-ID: <e73a5f99-7811-5155-5318-e630e871bff6@foss.arm.com> (raw)
In-Reply-To: <a264e810-a079-562a-4fba-322d52be5c3c@arm.com>

[-- Attachment #1: Type: text/plain, Size: 1769 bytes --]

Thanks.

Committed with the mentioned change. Patch in attachment for reference.

Best regards,

Thomas

On 15/02/17 11:26, Richard Earnshaw (lists) wrote:
> On 15/02/17 11:23, Thomas Preudhomme wrote:
>> Hi,
>>
>> ARMv5 and ARMv5E architectures have no known implementation. I therefore
>> suggest that we deprecate these architectures. ARMv5T, ARMv5TE and
>> ARMv5TEJ would remain supported though.
>>
>> Is this ok to commit?
>>
>> Best regards,
>>
>> Thomas
>>
>> deprecate_armv5_armv5e.patch
>>
>>
>> cvs diff: Diffing .
>> cvs diff: Diffing benchmarks
>> cvs diff: Diffing bugs
>
> "cvs -q diff" is your friend :-)
>
>> Index: gcc-7/changes.html
>> ===================================================================
>> RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-7/changes.html,v
>> retrieving revision 1.55
>> diff -u -r1.55 changes.html
>> --- gcc-7/changes.html	2 Feb 2017 15:21:11 -0000	1.55
>> +++ gcc-7/changes.html	14 Feb 2017 09:21:23 -0000
>> @@ -752,6 +752,13 @@
>>  <h3 id="arm">ARM</h3>
>>     <ul>
>>       <li>
>> +       Support for the ARMv5 and ARMv5E architectures has been deprecated and
>
> Suggest "Support for the ARMv5 and ARMv5E architectures (which have no
> known implementations) has been ..."
>
>> +       will be removed in a future GCC release.  Note that ARMv5T, ARMv5TE and
>> +       ARMv5TEJ architectures remain supported.
>> +       The values <code>armv5</code> and <code>armv5e</code> of
>> +       <code>-march</code> are thus deprecated.
>> +     </li>
>> +     <li>
>>         The ARMv8.2-A architecture and the ARMv8.2-A 16-bit Floating-Point
>>         Extensions are now supported.  They can be used by specifying the
>>         <code>-march=armv8.2-a</code> or <code>-march=armv8.2-a+fp16</code>
>
> Otherwise OK.
>
> R.
>

[-- Attachment #2: deprecate_armv5_armv5e.patch --]
[-- Type: text/x-patch, Size: 1007 bytes --]

Index: htdocs/gcc-7/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-7/changes.html,v
retrieving revision 1.55
diff -u -r1.55 changes.html
--- htdocs/gcc-7/changes.html	2 Feb 2017 15:21:11 -0000	1.55
+++ htdocs/gcc-7/changes.html	15 Feb 2017 11:35:49 -0000
@@ -752,6 +752,14 @@
 <h3 id="arm">ARM</h3>
    <ul>
      <li>
+       Support for the ARMv5 and ARMv5E architectures has been deprecated
+       (which have no known implementations) and will be removed in a future
+       GCC release.  Note that ARMv5T, ARMv5TE and ARMv5TEJ architectures
+       remain supported.
+       The values <code>armv5</code> and <code>armv5e</code> of
+       <code>-march</code> are thus deprecated.
+     </li>
+     <li>
        The ARMv8.2-A architecture and the ARMv8.2-A 16-bit Floating-Point
        Extensions are now supported.  They can be used by specifying the
        <code>-march=armv8.2-a</code> or <code>-march=armv8.2-a+fp16</code>

      reply	other threads:[~2017-02-16 17:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-15 11:26 Thomas Preudhomme
2017-02-15 11:46 ` Richard Earnshaw (lists)
2017-02-16 17:48   ` Thomas Preudhomme [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=e73a5f99-7811-5155-5318-e630e871bff6@foss.arm.com \
    --to=thomas.preudhomme@foss.arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=kyrylo.tkachov@arm.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).