This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Minor tweaks to documentation of scalar_storage_order
- From: Eric Botcazou <ebotcazou at adacore dot com>
- To: gcc-patches at gcc dot gnu dot org
- Date: Mon, 25 Jan 2016 12:42:31 +0100
- Subject: Minor tweaks to documentation of scalar_storage_order
- Authentication-results: sourceware.org; auth=none
Tested on x86_64-suse-linux, applied on the mainline as obvious.
2016-01-25 Eric Botcazou <ebotcazou@adacore.com>
* doc/extend.texi (scalar_storage_order type attribute): Fix typo and
improve wording for mixed storage order support.
--
Eric Botcazou
Index: doc/extend.texi
===================================================================
--- doc/extend.texi (revision 232773)
+++ doc/extend.texi (working copy)
@@ -6481,10 +6481,10 @@ integral type should be used.
When attached to a @code{union} or a @code{struct}, this attribute sets
the storage order, aka endianness, of the scalar fields of the type, as
well as the array fields whose component is scalar. The supported
-endianness are @code{big-endian} and @code{little-endian}. The attribute
+endiannesses are @code{big-endian} and @code{little-endian}. The attribute
has no effects on fields which are themselves a @code{union}, a @code{struct}
or an array whose component is a @code{union} or a @code{struct}, and it is
-possible to have fields with a different scalar storage order than the
+possible for these fields to have a different scalar storage order than the
enclosing type.
This attribute is supported only for targets that use a uniform default