public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Terry Guo <terry.guo@arm.com>
To: gcc-patches@gcc.gnu.org
Cc: gerald@pfeifer.com
Subject: [PATCH][wwwdocs] Update 5.0 changes.html with Thumb1 UAL
Date: Tue, 18 Nov 2014 02:59:00 -0000	[thread overview]
Message-ID: <20141118024816.GA27616@terry-pc01> (raw)

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

Hi there,

This patch documents recent Thumb-1 UAL feature in trunk. Is it OK?

BR,
Terry

[-- Attachment #2: document-thumb1-ual-v1.txt --]
[-- Type: text/plain, Size: 901 bytes --]

Index: changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-5/changes.html,v
retrieving revision 1.27
diff -u -r1.27 changes.html
--- changes.html	17 Nov 2014 20:14:38 -0000	1.27
+++ changes.html	18 Nov 2014 02:42:31 -0000
@@ -368,6 +368,16 @@
 
    </ul>
 
+<h3 id="arm">ARM</h3>
+     <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>
+
 <h2 id="os">Operating Systems</h2>
 
   <h3 id="dragonfly">DragonFly BSD</h3>

             reply	other threads:[~2014-11-18  2:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-18  2:59 Terry Guo [this message]
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

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=20141118024816.GA27616@terry-pc01 \
    --to=terry.guo@arm.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).