From patchwork Fri Jul 9 06:23:04 2010 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: doc patch for gengtype's tag Date: Thu, 08 Jul 2010 20:23:04 -0000 From: Basile Starynkevitch X-Patchwork-Id: 58355 Message-Id: <1278656584.8738.11.camel@glinka> To: gcc-patches@gcc.gnu.org Hello All, The following documentation patch to trunk rev 161983 clarifies the issue of "gengtype & many GTY tags for same union component?" http://gcc.gnu.org/ml/gcc/2010-07/msg00118.html & http://gcc.gnu.org/ml/gcc/2010-07/msg00061.html ############### patch::: ############### ############## gcc/ChangeLog entry ################ 2010-07-09 Basile Starynkevitch * doc/gty.texi (The inside of a GTY): Improved tag documentation. ############## Ok for trunk? Cheers Index: gcc/doc/gty.texi =================================================================== --- gcc/doc/gty.texi (revision 161983) +++ gcc/doc/gty.texi (working copy) @@ -183,6 +183,7 @@ The value of the expression given by @code{desc} i each @code{tag} value, each of which should be different. If no @code{tag} is matched, the field marked with @code{default} is used if there is one, otherwise no field in the union will be marked. +A union field can have at most one @code{tag}. In the @code{desc} option, the ``current structure'' is the union that it discriminates. Use @code{%1} to mean the structure containing it.