From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10942 invoked by alias); 19 Sep 2004 12:41:29 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 10917 invoked by alias); 19 Sep 2004 12:41:28 -0000 Date: Sun, 19 Sep 2004 12:41:00 -0000 Message-ID: <20040919124128.10915.qmail@sourceware.org> From: "giovannibajo at libero dot it" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20040910155309.17401.steven@gcc.gnu.org> References: <20040910155309.17401.steven@gcc.gnu.org> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug c++/17401] [3.4/4.0 Regression] ICE with invalid pure specifier X-Bugzilla-Reason: CC X-SW-Source: 2004-09/txt/msg02162.txt.bz2 List-Id: ------- Additional Comments From giovannibajo at libero dot it 2004-09-19 12:41 ------- Subject: Re: [3.4/4.0 Regression] ICE with invalid pure specifier steven at gcc dot gnu dot org wrote: > Isn't this just a matter of not filling > ridpointers with null_node as done below? Whenever RID_NULL > is encountered, we return just > null_node anyway, and there are apparently no other places where > ridpointers[RID_NULL] is read. I'll test this patch, let's see if > this helps. Maybe. But cp_parser_error is stil buggy and will ICE on other keywords (e.g. "public"/"protected"/"private") so thinking that is still desirable anyway. I'll get back to this bug later next week when I'm through with the finals. Giovanni Bajo -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17401