Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!njin!princeton!notecnirp!drh
From: drh@notecnirp.Princeton.EDU (Dave Hanson)
Newsgroups: gnu.gcc.bug
Subject: Re: GCC version number in .o files -- bad idea
Message-ID: <15625@princeton.Princeton.EDU>
Date: 15 Mar 89 01:52:35 GMT
References: <8903142103.AA18095@riunite.aca.mcc.com>
Sender: news@princeton.Princeton.EDU
Reply-To: drh@notecnirp.UUCP (Dave Hanson)
Distribution: gnu
Organization: Dept. of Computer Science, Princeton University
Lines: 15

In article <8903142103.AA18095@riunite.aca.mcc.com> rfg@MCC.COM (Ron Guilmette) writes:
	Dear John,
	
	This has been mentioned before to the gcc bug mailing lists.
	Somebody pointed out that for COFF files, you can get them
	to compare the same if you skip over the first few bytes of
	both files before starting the compare.  I've forgotten now
	what the suggested way of doing that was.  Anybody care to
	refresh my memory?
	

strip them, then skip the first 8 bytes.
nevertheless, time/version stamping .o files
is a nuisance as regression testing on a mips
machine will reveal. i hope gcc doesn't do it.