This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Bootstrap failure on irix6.5 possibly caused by new C++ parser?

From: Graham Stott <graham dot stott at btinternet dot com>
To: Mark Mitchell <mark at codesourcery dot com>
Cc: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>, "gcc at gcc dot gnu dot org"<gcc at gcc dot gnu dot org>
Date: Tue, 31 Dec 2002 20:01:12 +0000
Subject: Re: Bootstrap failure on irix6.5 possibly caused by new C++ parser?
References: <131330000.1041362249@warlock.codesourcery.com>

Mark Mitchell wrote:

--On Tuesday, December 31, 2002 07:11:41 PM +0000 Graham Stott <graham.stott@btinternet.com> wrote:

It's the "*ac = NULL_TREE" that's trampling over memory.

I suspect we are missing a bit of GTY(()) magic for the access_checks
list.

I think I can see why the access_list returned by
cp_parser_stop_deferring_access_checks are not accessible via a GTY(())
tagged root so they might be GC if collect kicks in.


Oh, heck.  That's annoying.  I do not like it that our GC stuff makes
us globalize local variables so that we can get them registered.

Anyhow, thanks for the debugging!  I will try to come up with a patch to
send you to test.

Thanks,

I'm already testing a patch which looks to fix the problem. It's past the last
point of failure and going well.

Graham

Follow-Ups:
- Re: Bootstrap failure on irix6.5 possibly caused by new C++ parser?
  - From: Mark Mitchell

References:
- Re: Bootstrap failure on irix6.5 possibly caused by new C++ parser?
  - From: Mark Mitchell

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]