This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: state of 3.2.1-pre: how far from release?
- From: Joe Buck <jbuck at synopsys dot com>
- To: dje at watson dot ibm dot com (David Edelsohn)
- Cc: Joe dot Buck at synopsys dot COM (Joe Buck), gcc at gcc dot gnu dot org
- Date: Tue, 5 Nov 2002 14:43:23 -0800 (PST)
- Subject: Re: state of 3.2.1-pre: how far from release?
I wrote:
> Joe> bootstrap/8362
> Joe> This is PowerPC specific and appears to be a blocker.
>
> Joe> 3.2.1 has a vast number of bug fixes over 3.2. If we can get 8362
> Joe> fixed, I'd say ship the sucker, it is in the best interest of the
> Joe> users to get the fixes out there (especially all the fixes to the
> Joe> x86 backend). The other bugs are not that important.
David Edelsohn writes:
> I can guard the source code in abi_check.cc which elicits the ICE
> so that the compiler will bootstrap. This will not fix the bug. The
> testcase takes a very long time to compile when running the compiler in
> the debugger, so it is difficult to debug. The rest of libstdc++-v3
> compiles, so this bug is not extremely common but it is not complicated
> either.
Perhaps that's the best thing for now. I would be satisfied with a
workaround for 3.2.1.
> Without help from GCC experts who understand the reload pass, this
> will take a while to debug and fix.
Don't we plan to redo/replace reload for 3.4? Or am I confused?
In any case: Mark, what's your thinking? Are there other bugs that you
consider blockers?
In any case, if (or rather, when) we release 3.2.1 with still-open
regressions, I'll add a description of the regressions to the release
notes.