From: "Terry Guo" <terry.guo@arm.com>
To: <gcc-patches@gcc.gnu.org>
Cc: <gerald@pfeifer.com>, "Kyrylo Tkachov" <Kyrylo.Tkachov@arm.com>,
<law@redhat.com>
Subject: RE: [PATCH][wwwdocs] Update 5.0 changes.html with Thumb1 UAL
Date: Thu, 20 Nov 2014 09:24:00 -0000 [thread overview]
Message-ID: <001b01d004a1$0a7c52f0$1f74f8d0$@arm.com> (raw)
In-Reply-To: <546B60D1.80002@arm.com>
> -----Original Message-----
> From: Kyrill Tkachov [mailto:kyrylo.tkachov@arm.com]
> Sent: Tuesday, November 18, 2014 11:08 PM
> To: Terry Guo; gcc-patches@gcc.gnu.org
> Cc: gerald@pfeifer.com
> Subject: Re: [PATCH][wwwdocs] Update 5.0 changes.html with Thumb1 UAL
>
>
> On 18/11/14 02:48, Terry Guo wrote:
> > + <ul>
> > + <li> The Thumb-1 assembly code are now generated in unified
syntax.
> The new option
> > + <code>-masm-syntax-unified</code> can be used to specify
whether
> inline assembly
> > + code are using unified syntax. By default the option is off
which
> means
> > + non-unified syntax is used. However this is subject to change
in future
> releases.
> > + Eventually the non-unified syntax will be deprecated.
> > + </li>
> > + </ul>
> Hi Terry,
>
> Sorry for the late comment, I see this has already been committed.
>
> I think it should be "assembly code is now generated".
> Also "whether inline assembly code is using unified syntax".
>
> Kyrill
Thanks for comments. I committed below patch to fix those typos.
BR,
Terry
Index: htdocs/gcc-5/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-5/changes.html,v
retrieving revision 1.39
diff -u -r1.39 changes.html
--- htdocs/gcc-5/changes.html 19 Nov 2014 12:13:00 -0000 1.39
+++ htdocs/gcc-5/changes.html 20 Nov 2014 03:48:26 -0000
@@ -387,9 +387,9 @@
<h3 id="arm">ARM</h3>
<ul>
- <li> The Thumb-1 assembly code are now generated in unified syntax.
The new option
+ <li> The Thumb-1 assembly code is now generated in unified syntax.
The new option
<code>-masm-syntax-unified</code> can be used to specify whether
inline assembly
- code are using unified syntax. By default the option is off which
means
+ code is using unified syntax. By default the option is off which
means
non-unified syntax is used. However this is subject to change in
future releases.
Eventually the non-unified syntax will be deprecated.
</li>
next prev parent reply other threads:[~2014-11-20 9:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 2:59 Terry Guo
2014-11-18 3:23 ` Jeff Law
2014-11-18 15:21 ` Kyrill Tkachov
2014-11-20 9:24 ` Terry Guo [this message]
2015-04-10 21:48 ` Gerald Pfeifer
2015-04-13 1:53 ` Terry Guo
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='001b01d004a1$0a7c52f0$1f74f8d0$@arm.com' \
--to=terry.guo@arm.com \
--cc=Kyrylo.Tkachov@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=law@redhat.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).