From 293c28eedb85fae6a8f7fd726b6c94553772b121 Mon Sep 17 00:00:00 2001 From: Gaute B Strokkenes Date: Tue, 19 Feb 2002 22:51:17 +0000 Subject: [PATCH] * doc/c-tree.texi (Classes, TYPE_BINFO): Fix typo. From-SVN: r49881 --- gcc/ChangeLog | 4 ++++ gcc/doc/c-tree.texi | 4 ++-- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 100b36b2d5b..22300213537 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,7 @@ +2002-02-19 Gaute B Strokkenes + + * doc/c-tree.texi (Classes, TYPE_BINFO): Fix typo. + 2002-02-19 Philip Blundell PR 5399 diff --git a/gcc/doc/c-tree.texi b/gcc/doc/c-tree.texi index 849d07948b6..afe18e50e7e 100644 --- a/gcc/doc/c-tree.texi +++ b/gcc/doc/c-tree.texi @@ -760,8 +760,8 @@ binfo is given by @code{BINFO_TYPE}. It is always the case that qualifiers. However, it is not always the case that @code{TYPE_BINFO (BINFO_TYPE (y))} is always the same binfo as @code{y}. The reason is that if @code{y} is a binfo representing a base-class @code{B} of a -derived class @code{D}, then @code{BINFO_TYPE (y)} will be @code{B}, and -@code{TYPE_INFO (BINFO_TYPE (y))} will be @code{B} as its own +derived class @code{D}, then @code{BINFO_TYPE (y)} will be @code{B}, +and @code{TYPE_BINFO (BINFO_TYPE (y))} will be @code{B} as its own base-class, rather than as a base-class of @code{D}. The @code{BINFO_BASETYPES} is a @code{TREE_VEC} (@pxref{Containers}). -- 2.30.2