public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
Cc: gcc-patches@gcc.gnu.org, richard.earnshaw@arm.com
Subject: Re: [RFA:] Caveat for ARM in gcc-4.7/changes.html: unaligned accesses, take 2
Date: Sat, 29 Dec 2012 17:36:00 -0000	[thread overview]
Message-ID: <alpine.LNX.2.00.1212290649520.15650@tuna.site> (raw)
In-Reply-To: <201206150207.q5F27NNC005016@ignucius.se.axis.com>

This is a small follow-up change that I had meant to commit for
a while (ahem); done now.

Thanks for taking the time to write this up!

Gerald

Index: changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.7/changes.html,v
retrieving revision 1.133
diff -u -3 -p -r1.133 changes.html
--- changes.html	3 Dec 2012 18:39:27 -0000	1.133
+++ changes.html	29 Dec 2012 17:34:01 -0000
@@ -53,15 +53,15 @@
     <li>On ARM, when compiling for ARMv6 (but not ARMv6-M), ARMv7-A,
     ARMv7-R, or ARMv7-M, the new option
     <code>-munaligned-access</code> is active by default, which for
-    some source codes generates code that accesses memory on unaligned
-    addresses.  This will require the kernel of those systems to enable
+    some sources generates code that accesses memory on unaligned
+    addresses.  This requires the kernel of those systems to enable
     such accesses (controlled by CP15 register <code>c1</code>, refer
-    to ARM documentation).  Alternatively or for compatibility with
+    to ARM documentation).  Alternatively, or for compatibility with
     kernels where unaligned accesses are not supported, all code has
     to be compiled with <code>-mno-unaligned-access</code>.
-    Linux/ARM in official releases has automatically and
+    Upstream Linux kernel releases have automatically and
     unconditionally supported unaligned accesses as emitted by GCC due
-    to this option being active, since Linux version 2.6.28.</li>
+    to this option being active since version 2.6.28.</li>
 
     <li>Support on ARM for the legacy floating-point accelerator (FPA) and
     the mixed-endian floating-point format that it used has been obsoleted.

      parent reply	other threads:[~2012-12-29 17:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-08  0:31 [RFA:] Caveat for ARM in gcc-4.7/changes.html: unaligned accesses Hans-Peter Nilsson
2012-06-08  3:20 ` Michael Hope
2012-06-08  3:51   ` Hans-Peter Nilsson
2012-06-08  4:29     ` Michael Hope
2012-06-08  4:53       ` Hans-Peter Nilsson
2012-06-08  5:17         ` Hans-Peter Nilsson
2012-06-10 22:27           ` Michael Hope
2012-06-10 23:16             ` Hans-Peter Nilsson
2012-06-12 14:37               ` Hans-Peter Nilsson
2012-06-12 23:15                 ` Michael Hope
2012-06-13  2:19                   ` Hans-Peter Nilsson
2012-06-10 23:00 ` Gerald Pfeifer
2012-06-11  1:29   ` Hans-Peter Nilsson
2012-06-13 13:55     ` Hans-Peter Nilsson
2012-06-15  3:40       ` [RFA:] Caveat for ARM in gcc-4.7/changes.html: unaligned accesses, take 2 Hans-Peter Nilsson
2012-06-22  7:20         ` Ping: " Hans-Peter Nilsson
2012-06-29 13:35           ` Hans-Peter Nilsson
2012-07-08  1:10             ` Ping again: " Hans-Peter Nilsson
2012-12-29 17:36         ` Gerald Pfeifer [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=alpine.LNX.2.00.1212290649520.15650@tuna.site \
    --to=gerald@pfeifer.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hans-peter.nilsson@axis.com \
    --cc=richard.earnshaw@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).