Jean-Marc Ottorini wrote:
I am still trying to build the gpc-20000719 / gcc-2.95.2 suite on top of Irix 6.5.
Following Frank Heckenbach advice to replace BYTES_BIG_ENDIAN by 0 in line 64 of stor-layout.c, the compilation process has progressed but is again stopped many steps further by the following error:
--
/usr/people/ottorini/pascal/gcc-2.95.2/gcc/p/rts/string.pas:224: Internal compiler error in `add_bound_info', at gcc-2.95.2/gcc/dwarf2out.c:7376
Please submit a full bug report.
See URL:http://www.gnu.org/software/gcc/faq.html#bugreport for instructions. gmake[2]: *** [string.o] Error 1 gmake[2]: Leaving directory `/usr/people/ottorini/pascal/gpc-build/gcc/p/rts' gmake[1]: *** [pascal.rts] Error 2 gmake[1]: Leaving directory `/usr/people/ottorini/pascal/gpc-build/gcc' gmake: *** [all-gcc] Error 2
Function `Memcompcase' reads:
function MemCompCase (const s1, s2; Size : SizeType) : Boolean; var i : Integer; a1 : array [1 .. Size] of Char absolute s1; a2 : array [1 .. Size] of Char absolute s2; begin for i := 1 to Size do if (a1 [i] <> a2 [i]) and (LoCase (a1 [i]) <> LoCase (a2 [i])) then return False; MemCompCase := True end;
Personnally, I cannot see what is harmful here (the problem persists after consistently replacing BYTES_BIG_ENDIAN by 0 in dwarf2out.c)
I don't think you should've done that. What I meant was that the initialization of the variable set_words_big_endian doesn't matter, but the value of BYTES_BIG_ENDIAN elsewhere does matter, and might explain the problem described. Since it's not used as an initialization in dwarf2out.c, I don't suppose there are compiling problems when leaving BYTES_BIG_ENDIAN there. It's just the one place in stor-layout.c where it should be changed.
Frank