On 11/04/2011 04:34 PM, Joseph S. Myers wrote:
Likewise.
I think I got all those, plus a couple of more I noticed along the way.
* doc/extend.texi: Document __atomic built-in functions.
* doc/invoke.texi: Document data race parameters.
* doc/md.texi: Document atomic p
On Fri, 4 Nov 2011, Andrew MacLeod wrote:
> + GCC will allow any integral scalar or pointer type that is 1, 2, 4, or 8
> + bytes in length. 16 bytes integral types are also allowed if
"16 bytes" appears to be used as an adjective; "16-byte" would be better.
> + @samp{__int128_t} is supported by
On 11/03/2011 08:04 PM, Joseph S. Myers wrote:
On Thu, 3 Nov 2011, Andrew MacLeod wrote:
Index: doc/extend.texi
Generally watch the line lengths in this patch - you should rewrap the
paragraphs to a width of about 70 characters (no more than 80) before
putting them on trunk. @item, @deftypefn
I don't see any changes to md.texi to document how machine descriptions
should implement the new functionality, either here or in any other patch
in the series, but such documentation is certainly required.
--
Joseph S. Myers
jos...@codesourcery.com
On Thu, 3 Nov 2011, Andrew MacLeod wrote:
> Index: doc/extend.texi
Generally watch the line lengths in this patch - you should rewrap the
paragraphs to a width of about 70 characters (no more than 80) before
putting them on trunk. @item, @deftypefn etc. lines that can't be wrapped
may be long
These are the documentation changes for the __atomic builtins.
Changefile entries are part of the gcc patch.
Index: doc/extend.texi
===
*** doc/extend.texi (.../trunk/gcc) (revision 180790)
--- doc/extend.texi (.../branches/
