public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: James Greenhalgh <james.greenhalgh@arm.com>
To: Kyrill Tkachov <kyrylo.tkachov@foss.arm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, <nd@arm.com>
Subject: Re: [PATCH][wwwdocs] Improve arm and aarch64-related info in readings.html
Date: Mon, 23 May 2016 08:56:00 -0000	[thread overview]
Message-ID: <20160523085552.GA7147@arm.com> (raw)
In-Reply-To: <573DDB63.40101@foss.arm.com>

On Thu, May 19, 2016 at 04:27:31PM +0100, Kyrill Tkachov wrote:
> Hi all,
> 
> I noticed that we have a readings.html page that has pointers to
> documentation of various backends that GCC supports.  The info on arm seems a
> bit out of date and somewhat confusing, and there is no entry for aarch64.
> This patch tries to address that.
> 
> The arm entry is updated to not mention armv2(?) and thumb and an aarch64
> entry is added with a link to the ARM documentation.
> 
> Ok to commit?

The AArch64 part looks fine to me, but a paragraph introducing what is
meant by AArch64 ("the 64-bit execution state introduced in the ARMv8-A
architecture profile" - or similar) would be a useful addition. Just
sending our users straight to the full repository of information provided
by ARM may give them too wide a set of readings :).

Thanks,
James

> ? readings.html~
> Index: readings.html
> ===================================================================
> RCS file: /cvs/gcc/wwwdocs/htdocs/readings.html,v
> retrieving revision 1.242
> diff -U 3 -r1.242 readings.html
> --- readings.html	14 Nov 2015 23:40:21 -0000	1.242
> +++ readings.html	15 Feb 2016 13:29:03 -0000
> @@ -59,6 +59,11 @@
>  </p>
>  
>  <ul>
> + <li>AArch64
> +  <br /><a href="http://infocenter.arm.com/help/index.jsp">
> +	ARM Documentation</a>
> + </li>
> +
>   <li>alpha
>     <br />Manufacturer: Compaq (DEC)
>     <br /><a href="http://www.tru64unix.compaq.com/docs/base_doc/DOCUMENTATION/V51A_HTML/ARH9MBTE/TITLE.HTM">Calling
> @@ -81,12 +86,12 @@
>    <br /><a href="http://www.synopsys.com/IP/PROCESSORIP/ARCPROCESSORS/Pages/default.aspx">ARC Documentation</a>
>   </li>
>  
> - <li>arm (armv2, thumb)
> -  <br />Manufacturer: Various, by license from ARM
> + <li>ARM
> +  <br />Manufacturer: Various, by license from ARM.
>    <br />CPUs include: ARM7 and ARM7T series (eg. ARM7TDMI), ARM9 and StrongARM
>    <br /><a href="http://infocenter.arm.com/help/index.jsp">ARM Documentation</a>
>   </li>
> - 
> +
>   <li>AVR
>    <br />Manufacturer: Atmel
>    <br /><a href="http://www.atmel.com/products/microcontrollers/avr/">AVR Documentation</a>

  reply	other threads:[~2016-05-23  8:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-19 15:27 Kyrill Tkachov
2016-05-23  8:56 ` James Greenhalgh [this message]
2016-05-29  7:59 ` Gerald Pfeifer
2016-05-31 10:10   ` Kyrill Tkachov
2016-06-02  9:29   ` 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=20160523085552.GA7147@arm.com \
    --to=james.greenhalgh@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=kyrylo.tkachov@foss.arm.com \
    --cc=nd@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).