variants: avoid type punning issue

[bison.git] / doc / bison.texi

diff --git a/doc/bison.texi b/doc/bison.texi
index 7a36f854e2794e8a846f8141a9928f3afef5d587..1218b5837165e37dc78715eb6864a49375880642 100644 (file)
--- a/doc/bison.texi
+++ b/doc/bison.texi
@@ -10268,14 +10268,6 @@ therefore, since, as far as we know, @code{double} is the most demanding
 type on all platforms, alignments are enforced for @code{double} whatever
 types are actually used.  This may waste space in some cases.
 
 type on all platforms, alignments are enforced for @code{double} whatever
 types are actually used.  This may waste space in some cases.
 

-@item
-Our implementation is not conforming with strict aliasing rules.  Alias
-analysis is a technique used in optimizing compilers to detect when two
-pointers are disjoint (they cannot ``meet'').  Our implementation breaks
-some of the rules that G++ 4.4 uses in its alias analysis, so @emph{strict
-alias analysis must be disabled}.  Use the option
-@option{-fno-strict-aliasing} to compile the generated parser.
-

 @item
 There might be portability issues we are not aware of.
 @end itemize
 @item
 There might be portability issues we are not aware of.
 @end itemize