Xref: utzoo comp.unix.ultrix:3665 gnu.gcc:1652 Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!dali.cs.montana.edu!milton!uw-beaver!cornell!alg From: alg@cornell.UUCP (Anne Louise Gockel) Newsgroups: comp.unix.ultrix,gnu.gcc Subject: GCC 1.37.1 on a DECsystem 3100 Message-ID: <41714@cornell.UUCP> Date: 4 Jun 90 20:31:38 GMT Reply-To: alg@cs.cornell.edu (Anne Louise Gockel) Distribution: comp Organization: Cornell Univ. CS Dept, Ithaca NY Lines: 73 I followed the proceedures for compiling gcc 1.37.1 on a DECsystem 3100 running UWS 2.2 / Ultrix 3.1. 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 52284 62 64 52285 70 65 c-parse.tab.o 84669 70 67 84670 61 64 84671 62 63 84672 62 71 c-typeck.o 57886 70 67 57887 61 64 57888 63 65 57889 64 61 caller-save.o 4177 70 67 4178 63 67 4179 70 60 4180 65 62 cccp.o 90622 70 67 90623 64 70 90624 70 60 90625 71 67 cexp.o 12782 70 67 12783 64 70 12784 71 61 12785 65 63 combine.o 48006 70 67 48007 63 66 48008 64 66 48009 71 63 cse.o 52077 70 67 52078 63 66 52079 62 63 52080 62 71 dbxout.o emit-rtl.o 16013 70 67 16014 62 66 16015 70 60 16016 64 61