This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
c++ add rid entries for choose_expr and types_compatible_p
- From: Aldy Hernandez <aldyh at redhat dot com>
- To: David Edelsohn <dje at watson dot ibm dot com>
- Cc: George France <france at handhelds dot org>, gcc patches <gcc-patches at gcc dot gnu dot org>
- Date: 08 Dec 2001 23:53:50 -0800
- Subject: c++ add rid entries for choose_expr and types_compatible_p
- References: <200112090711.CAA27846@makai.watson.ibm.com>
On Sat, 2001-12-08 at 23:11, David Edelsohn wrote:
> >>>>> George France writes:
>
> George> gcc from the HEAD cvs tree snapshot that I took an hour ago is failing to
> George> build on i686-pc-linux-gnu, as follows:
>
> George> It built correctly from the cvs snapshot that I took 24 hours ago. Any Ideas
> George> what has changed???
>
> Are you sure that c-parse.in did not change between the phases?
> That is exactly the files affected by Aldy's patch. If not, you might try
> reverting Aldy's patch because his report of libstdc++ build failure is
> worrisome.
from cp/lex.c and c-parse.in:
/* Table mapping from RID_* constants to yacc token numbers.
Unfortunately we have to have entries for all the keywords in all
three languages. */
hmm..
objc is ok because objc-parse.y is generated automatically from c-parse.in
c++ is another story.
committed as obvious. bootstrapped fixed.
--
Aldy Hernandez E-mail: aldyh@redhat.com
Professional Gypsy
Red Hat, Inc.
2001-12-08 Aldy Hernandez <aldyh@redhat.com>
* lex.c (rid_to_yy): Add RID_CHOOSE_EXPR and
RID_TYPES_COMPATIBLE_P.
Index: cp/lex.c
===================================================================
RCS file: /cvs/uberbaum/gcc/cp/lex.c,v
retrieving revision 1.259
diff -c -p -r1.259 lex.c
*** lex.c 2001/12/01 18:42:42 1.259
--- lex.c 2001/12/09 07:45:07
*************** const short rid_to_yy[RID_MAX] =
*** 563,568 ****
--- 563,570 ----
/* RID_PTRBASE */ 0,
/* RID_PTREXTENT */ 0,
/* RID_PTRVALUE */ 0,
+ /* RID_CHOOSE_EXPR */ 0,
+ /* RID_TYPES_COMPATIBLE_P */ 0,
/* RID_FUNCTION_NAME */ VAR_FUNC_NAME,
/* RID_PRETTY_FUNCTION_NAME */ VAR_FUNC_NAME,