On 04/21/2016 10:26 AM, Wilco Dijkstra wrote:

diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 
e9763d44d8d7aa6a64821a4b1811e55025aaaa4e..ddd4eeaec1502f871d0febd6045e37153c48a7e1
 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -12827,9 +12827,9 @@ These options are defined for AArch64 implementations:
  @item -mabi=@var{name}
  @opindex mabi
  Generate code for the specified data model.  Permissible values
-are @samp{ilp32} for SysV-like data model where int, long int and pointer
+are @samp{ilp32} for SysV-like data model where int, long int and pointers
  are 32-bit, and @samp{lp64} for SysV-like data model where int is 32-bit,
-but long int and pointer are 64-bit.
+but long int and pointers are 64-bit.

Can you please change all the incorrectly hyphenated "32-bit" and "64-bit" uses in this section to "32 bits" and "64 bits" respectively? ("n-bit" should only be hyphenated when it is used as an adjective phrase immediately before the noun it modifies.)

@@ -12872,7 +12871,8 @@ statically linked only.

  @item -mstrict-align
  @opindex mstrict-align
-Do not assume that unaligned memory references are handled by the system.
+Avoid generating unaligned accesses when accessing objects at non-naturally
+aligned boundaries as described in the architecture.

The new text seems repetitive and awkward to me.  How about something like:

Avoid generating memory accesses that may not be aligned on a natural object boundary as described in the architecture specification.

??

@@ -12916,10 +12916,11 @@ corresponding flag to the linker.
  @item -mno-low-precision-recip-sqrt
  @opindex -mlow-precision-recip-sqrt
  @opindex -mno-low-precision-recip-sqrt
-When calculating the reciprocal square root approximation,
-uses one less step than otherwise, thus reducing latency and precision.
-This is only relevant if @option{-ffast-math} enables the reciprocal square 
root
-approximation, which in turn depends on the target processor.
+Enable or disable reciprocal square root approximation.
+This option only has an effect if @option{-ffast-math} or
+@option{-funsafe-math-optimizations} is used as well.  Enabling this reduces
+precision of reciprocal square root results to about 16 bits for
+single-precision and to 32 bits for double-precision.

"single precision" and "double precision" should not be hyphenated when used as nouns, as they are here (only when used as an adjective phrase immediately before the noun they modify).

@@ -13010,10 +13003,10 @@ This option is only intended to be useful when 
developing GCC.

  @item -mpc-relative-literal-loads
  @opindex mpcrelativeliteralloads

What happened to that @opindex entry?  :-(

-Enable PC relative literal loads. If this option is used, literal
-pools are assumed to have a range of up to 1MiB and an appropriate
-instruction sequence is used. This option has no impact when used
-with @option{-mcmodel=tiny}.
+Enable PC relative literal loads.  With this option literal pools are

"PC-relative" should be hyphenated since this *is* and adjective phrase immediately before the noun it modifies....

-Sandra the nit-picky

Reply via email to