From: Terry Guo <flameroc@gmail.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH][wwwdocs] Update 5.0 changes.html with Thumb1 UAL
Date: Mon, 13 Apr 2015 01:53:00 -0000 [thread overview]
Message-ID: <CAGbRaL4RKqJuaYz_xREFBTjgEeUcnYy8Qv5ecVqgwDNCuv-b+g@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.20.1504102347210.9357@tuna.site>
On Sat, Apr 11, 2015 at 5:48 AM, Gerald Pfeifer <gerald@pfeifer.com> wrote:
> Hi Terry,
>
> I went ahead and committed some small changes to the description of
> -masm-syntax-unified. Let me know if you disagree or would like to
> see further changes.
>
> Gerald
>
Thanks for the improvement. I am totally ok with them.
BR,
Terry
> Index: changes.html
> ===================================================================
> RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-5/changes.html,v
> retrieving revision 1.101
> diff -u -r1.101 changes.html
> --- changes.html 9 Apr 2015 23:30:47 -0000 1.101
> +++ changes.html 10 Apr 2015 21:47:01 -0000
> @@ -636,8 +636,8 @@
>
> <h3 id="arm">ARM</h3>
> <ul>
> - <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
> + <li>Thumb-1 assembly code is now generated in unified syntax. The new option
> + <code>-masm-syntax-unified</code> specifies whether inline assembly
> 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.
prev parent reply other threads:[~2015-04-13 1:53 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
2015-04-10 21:48 ` Gerald Pfeifer
2015-04-13 1:53 ` Terry Guo [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=CAGbRaL4RKqJuaYz_xREFBTjgEeUcnYy8Qv5ecVqgwDNCuv-b+g@mail.gmail.com \
--to=flameroc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.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).