On Wed, Mar 14, 2012 at 2:57 PM, Gerald Pfeifer <ger...@pfeifer.com> wrote:
> On Wed, 14 Mar 2012, Uros Bizjak wrote:
>> I have also added Gerald to CC, to check if everything is OK with
>> added documentation.
>
> Joseph is better with that than I am, but I'll give it a try. :-)
>
> +@item -maddress-mode=long
> +@opindex maddress-mode=long
> +Generate code for long address mode. It is only supported for 64-bit
> +and x32 environments. This is the default address mode for 64-bit
> +environment.
>
> I cannot formally explain why, but would swap "It" and "This" in
> this paragraph and the other.
>
> In any case "64-bit environments" (Plural).
>
> Fine with these changes.
I checked in the updated patch.
>
> Apart from the above, at least invoke.texi does not define what an x32
> environment is. Shouldn't that done somewhere (before this terminology
> is used)?
>
I am not sure where to put it. In any case, here is a patch to update
GCC 4.7.0 changes with link to x32 website.
--
H.J.
Index: htdocs/gcc-4.7/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.7/changes.html,v
retrieving revision 1.96
diff -u -p -r1.96 changes.html
--- htdocs/gcc-4.7/changes.html 7 Mar 2012 14:15:35 -0000 1.96
+++ htdocs/gcc-4.7/changes.html 14 Mar 2012 22:31:50 -0000
@@ -720,6 +720,8 @@ int add_values (const __flash int *p, in
for Windows mingw targets.</li>
<li>Support for new AMD family 15h processors (Piledriver core) is now available
through <code>-march=bdver2</code> and <code>-mtune=bdver2</code> options.</li>
+ <li>Support for <a href="http://sites.google.com/site/x32abi/";>x32 psABI</a>
+ is now available through <code>-mx32</code> option.
<li>...</li>
</ul>
