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


"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
keep pushing - without, I might add, any indication that it does
prevent the bug from manifesting - disables an important space
optimization; depending on the configuration, that logic can reduce
the size of the final cc1 by hundreds of KB.

You are, as I said earlier, welcome to turn it off in your source tree
if that makes finding the real bug easier for you, but please stop
submitting the patch as if it were fixing the real bug.

zw


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