public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "giovannibajo at libero dot it" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/17401] [3.4/4.0 Regression] ICE with invalid pure specifier
Date: Sun, 19 Sep 2004 12:41:00 -0000	[thread overview]
Message-ID: <20040919124128.10915.qmail@sourceware.org> (raw)
In-Reply-To: <20040910155309.17401.steven@gcc.gnu.org>


------- 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


  parent reply	other threads:[~2004-09-19 12:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-10 15:53 [Bug c++/17401] New: ICE with checking after parse error (?) steven at gcc dot gnu dot org
2004-09-10 15:53 ` [Bug c++/17401] " steven at gcc dot gnu dot org
2004-09-10 18:40 ` [Bug c++/17401] [4.0 Regression] " belyshev at lubercy dot com
2004-09-10 18:46 ` bangerth at dealii dot org
2004-09-10 22:25 ` pinskia at gcc dot gnu dot org
2004-09-10 23:52 ` giovannibajo at libero dot it
2004-09-11  0:33 ` [Bug c++/17401] [3.4/4.0 " giovannibajo at libero dot it
2004-09-11 13:09 ` [Bug c++/17401] [3.4/4.0 Regression] ICE with invalid pure specifier giovannibajo at libero dot it
2004-09-12 22:46 ` bangerth at dealii dot org
2004-09-19 12:21 ` steven at gcc dot gnu dot org
2004-09-19 12:41 ` giovannibajo at libero dot it [this message]
2004-09-19 12:45 ` giovannibajo at libero dot it
2004-09-27 12:05 ` giovannibajo at libero dot it
2004-12-23 22:20 ` mmitchel at gcc dot gnu dot org
2005-01-06 22:57 ` pinskia at gcc dot gnu dot org
2005-01-25 19:14 ` pinskia at gcc dot gnu dot org
2005-04-27 14:54 ` pinskia at gcc dot gnu dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040919124128.10915.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).