Path: utzoo!yunexus!telly!ddsw1!mcdchg!rutgers!apple!vsi1!daver!cheers!exodus
From: exodus@cheers.uucp (Greg Onufer)
Newsgroups: gnu.gcc.bug
Subject: Re: Bug in gcc-1.31 on SysV386
Message-ID: <212@cheers.uucp>
Date: 24 Nov 88 18:37:31 GMT
Article-I.D.: cheers.212
References: <8811231738.AA18183@satyr.UUCP>
Distribution: gnu
Organization: Cheers Bar & Grill, Boston
Lines: 26

From article <8811231738.AA18183@satyr.UUCP>, by satyr!local@APPLE.COM (Local Development):
> I just finished compiling gcc-1.31 on my system!! Yeah!! (Thank you,
> FSF!).
> 
> My system is: Altos 1000 running Unix System 5.3.1b. It's a
> 386 box.
> 
> Examining ho.o and ho.o.orig, the *only* place they differ is character
> 5, which seems to be set to a random value at each compilation (with the
> same compiler!).

Try looking up the COFF file format in your system documentation or in
your header files... 

A few bytes at the beginning of the file change from compilation
to compilation (I think I got bytes 5 & 6 changed on a Sun Roadrunner--
no flames, Sun 386i's DO USE COFF, not BSD a.out files).

Use "cmp -l" to compare your .o files, and it should give you more
information to help you decide which files really differ in important
ways.

--greg
-- 
Greg Onufer .. University of the Pacific .. Focus Semiconductor
.. exodus@cheers.uucp .. sun!daver!cheers!exodus .. 415-965-0604