From: Kyrill Tkachov <kyrylo.tkachov@arm.com>
To: Terry Guo <terry.guo@arm.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: "gerald@pfeifer.com" <gerald@pfeifer.com>
Subject: Re: [PATCH][wwwdocs] Update 5.0 changes.html with Thumb1 UAL
Date: Tue, 18 Nov 2014 15:21:00 -0000 [thread overview]
Message-ID: <546B60D1.80002@arm.com> (raw)
In-Reply-To: <20141118024816.GA27616@terry-pc01>
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
next prev parent reply other threads:[~2014-11-18 15:08 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 [this message]
2014-11-20 9:24 ` Terry Guo
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=546B60D1.80002@arm.com \
--to=kyrylo.tkachov@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=terry.guo@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).