Displaying 2 results from an estimated 2 matches for "00001180".
Did you mean:
00001100
2007 Apr 30
0
[LLVMdev] Boostrap Failure -- Expected Differences?
...952
> -00000427 l O .rodata 00000012 __FUNCTION__.21033
> +0000041c l O .rodata 0000000b __FUNCTION__.20866
> +00000427 l O .rodata 00000012 __FUNCTION__.20946
> 00000108 l O .bss 00000004 reg_known_equiv_p
> 00001120 l F .text 00000029 set_reg_known_value
> 00001180 l F .text 00000026 set_reg_known_equiv_p
> 000012d0 l F .text ffffee04 rtx_equal_for_memref_p
> -00000439 l O .rodata 00000017 __FUNCTION__.21160
> -00000450 l O .rodata 0000000f __FUNCTION__.21323
> +00000439 l O .rodata 00000017 __FUNCTION__.21073
> +00000450 l...
2007 Apr 27
2
[LLVMdev] Boostrap Failure -- Expected Differences?
The saga continues.
I've been tracking the interface changes and merging them with
the refactoring work I'm doing. I got as far as building stage3
of llvm-gcc but the object files from stage2 and stage3 differ:
warning: ./cc1-checksum.o differs
warning: ./cc1plus-checksum.o differs
(Are the above two ok?)
The list below is clearly bad. I think it's every object file in
the