This is the mail archive of the gcc-patches@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: PATCH: [3.3 branch] IA64 bootstrap failure


On Tue, Jul 08, 2003 at 10:45:09PM -0700, Zack Weinberg wrote:
> "H. J. Lu" <hjl@lucon.org> writes:
> 
> >> 
> >> Why are you comparing stage1 and stage2, when the proper comparison is
> >> stage2 and stage3, which will have the same source files?
> >
> > Let me get this straight:
> >
> > 1. .o files under gcc/stage1/ are compiled by the bootstrap compiler.
> > 2. .o files under gcc/stage2/ are compiled by the stage1 compiler.
> > 3. .o files under gcc/ are compiler by the stage2 compiler.
> >
> > Since we compare .o files under gcc/stage2/ against .o files under gcc/,
> > why shouldn't I compare .c files under gcc/stage1/ against gcc/stage2/
> > for differences between stage1 and stage2 compiler sources.
> 
> I am 100% certain that the problem is not with insn-conditions.c;
> disabling the optimization it performs may perturb the bug out of its
> manifestation envelope, but the bug remains.  Meanwhile, the patch you

What do you mean by "bug"? As I said, the file is NOT miscompiled. It is
just different. Since compiler sources are different, comparison of
generated .o files don't mean much here. We have several choices:

1. Check each comparison failure to see if it is really miscompiled. Or
2. Add stage4 and compare against stage3, instead of stage2. Or
3. Make sure stage1 and stage2 have the same source files.


H.J.


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