extend.texi: Remove old claim that typedefs cannot have an alignment attribute.

	* doc/extend.texi: Remove old claim that typedefs cannot have
	an alignment attribute.

From-SVN: r52180

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 58f921dec24fe9af52cc58d4ccbe311aafcd6885..55e343e8f68eff596b24447e336185b9b0bb9867 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,8 @@
+2002-04-11  Richard Sandiford  <rsand
+
+       * doc/extend.texi: Remove old claim that typedefs cannot have
+       an alignment attribute.
+
 2002-04-11  Jakub Jelinek  <jakub@redhat.com>
 
        PR optimization/6177

diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
index f1f499d8b576f6d5296526f0f477ad1d5d85a1e4..2545acfa23b995c059ca968ed7a897cb60c860bb 100644 (file)
--- a/gcc/doc/extend.texi
+++ b/gcc/doc/extend.texi
@@ -2866,11 +2866,6 @@ struct foo @{ int x[2] __attribute__ ((aligned (8))); @};
 This is an alternative to creating a union with a @code{double} member
 that forces the union to be double-word aligned.
 
-It is not possible to specify the alignment of functions; the alignment
-of functions is determined by the machine's requirements and cannot be
-changed.  You cannot specify alignment for a typedef name because such a
-name is just an alias, not a distinct type.
-
 As in the preceding examples, you can explicitly specify the alignment
 (in bytes) that you wish the compiler to use for a given variable or
 structure field.  Alternatively, you can leave out the alignment factor