This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/11341] [cygwin] [pch] ICE in ggc_pop_context, at ggc-page.c:1441 while compiling libstc++3
- From: "geoffk at geoffk dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 28 Jun 2003 20:33:39 -0000
- Subject: [Bug bootstrap/11341] [cygwin] [pch] ICE in ggc_pop_context, at ggc-page.c:1441 while compiling libstc++3
- References: <20030626234311.11341.giovannibajo@libero.it>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11341
------- Additional Comments From geoffk at geoffk dot org 2003-06-28 20:33 -------
Subject: Re: [cygwin] [pch] ICE in ggc_pop_context, at ggc-page.c:1441 while compiling libstc++3
> Date: 28 Jun 2003 20:06:33 -0000
> From: "giovannibajo at libero dot it" <gcc-bugzilla@gcc.gnu.org>
> ------- Additional Comments From giovannibajo at libero dot it 2003-06-28 20:06 -------
> Subject: Re: [cygwin] [pch] ICE in ggc_pop_context, at ggc-page.c:1441 while compiling libstc++3
>
> geoffk at geoffk dot org <gcc-bugzilla@gcc.gnu.org> wrote:
>
> > No, I've never seen this before. It's probably specific to Cygwin. I
> > doubt that a reduced testcase would be very interesting. It seems to
> > be a random-memory-corruption bug, and so there's no guarantee that
> > it's actually related to PCH at all; but it's well worth tracking
> > down. I would start by spending some time with the debugger.
>
> Geoff, do you have any patch to completely disable PCH during bootstrap? At
> least that would be a check if it's PCH related or not.
That wouldn't prove that it's really anything to do with PCH. It
could be a random memory corruption bug that just happens to only turn
up when PCH is in use.
> Besides, I was able to bootstrap cygwin with no problems till two weeks ago.
> Can you think of any patches in this timeframe that might have
> caused/uncovered this problem?
No, but it might be interesting to find if there's one patch that
caused the problem to appear.