Xref: utzoo comp.unix.ultrix:3679 gnu.gcc:1655 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker!bloom-beacon!eru!luth!sunic!mcsun!hp4nl!serc!bogaart From: bogaart@serc.serc.nl (Eugene &) Newsgroups: comp.unix.ultrix,gnu.gcc Subject: Re: GCC 1.37.1 on a DECsystem 3100 Message-ID: Date: 5 Jun 90 10:03:41 GMT References: <41714@cornell.UUCP> Sender: bogaart@serc.nl Distribution: comp Organization: SERC Lines: 64 In-reply-to: alg@cornell.UUCP's message of 4 Jun 90 20:31:38 GMT In article <41714@cornell.UUCP> alg@cornell.UUCP (Anne Louise Gockel) writes: The procedures suggest that you build gcc once with the Ultrix cc compiler, a second time with the gcc compiler and a third time with the new gcc in order to compare the binaries. When I compared the binaries in the manner specified in Step 10) of the INSTALL document, I found that many of the files had differences beyond just the date stamp. The differences were extremely regular, almost as if there was a datestamp in the middle of the file. Has anyone run into this problem? Have I made a mistake in the installation procedure? Is there a good explanation for these differences? Thank you, Anne Louise Gockel Cornell Computer Science Internet: alg@cs.cornell.edu ---------- Partial list of differences from the "cmp -l" command, comparing the stage2 and the stage3 .o files: ---------- c-convert.o 4838 70 67 4839 61 64 4840 64 65 4841 60 67 c-decl.o 52282 70 67 52283 61 64 etc... I had the same problem with gcc 1.36, but I looked a bit further and found that the so called differences are: diff ../testdiff/c-convert.o.hexl ./c-convert.o.hexl 1c1 < 00000000: 6201 0300 0eec 5826 3412 0000 6000 0000 b.....X&4...`... --- > 00000000: 6201 0300 9df8 5726 3412 0000 6000 0000 b.....W&4...`... 405c405 < 00001940: 722f 746d 702f 6363 6130 3635 3130 2e73 r/tmp/cca06510.s --- > 00001940: 722f 746d 702f 6363 6130 3334 3339 2e73 r/tmp/cca03439.s According to me this is harmless, because they don't differ a lot ! The above output of a special diff shows that the first lines differ and that half way the file is another difference. I have tested it, and it appears to be in every *.o file. It is, I think, the name of the intermediate assembler file where the *.o file is generated from (but this is a guess !). Further I did not experience many problems in using gcc (1.36) on the DEC Stations, but I did not use it extensively. Eugene -- Name: Eugene Bogaart | Software Engineering Research Centre Email: bogaart@serc.nl | Lange Viestraat 365 3511 BK Utrecht Phone: +31 30 32 26 40 | P.box 424 3500 AK Utrecht Fax: +31 30 34 12 49 | The Netherlands