🚀 go-pugleaf

In article <9002220202.AA10288@sturgeon.cs.washington.edu> pardo@STURGEON.CS.WASHINGTON.EDU (David Keppel) writes:

>   Machine: DECstation 3100
>   Config: config.gcc decstation
>   Gcc: gcc 1.37 (prep.ai.mit.edu, 20 Feb., 1990)

[stuff deleted]
   *4

   Nearly every gcc file compiled with stage2 differs from the
   stage1-compiled file, even ignoring the first bytes.

   $ for file in *.o; do
   > echo $file
   > tail +10 $file > foo1
   > tail +10 stage2/$file > foo2
   > cmp foo1 foo2
   > done
   c-convert.o
   foo1 foo2 differ: char 4837, line 29
   c-decl.o
   foo1 foo2 differ: char 52281, line 113

   [... and so on. ]

   I tried doing the following: compile each .c using stage1/gcc -S and
   using stage2/gcc -S, then compare the assembly files.  In each case,
   the assembly was the same.  Unless I screwed up, it is the assembler,
   not gcc, that is causing the difference.


	   ;-D on  ( Brought to you by the makers of... )  Pardo

Compiling a 'hello world' program and visit the binary (.o) with emacs
reveal that it is the name of the /tmp/as???? file that is put in the
object file. Try two subsequent compilations.

--
------------------------ ORIGIN  '~jnp/stdDisclaimers' ------------------------
| Regards, J|rgen N|rgaard ('|' is '\o{}' in \LaTeX{})                        |
|    e-mail: jnp@tele.nokia.fi | telephone: <..>-358-0-511-5671               |
--        mail: Nokia Telecommunications, PL 33, SF-02601 Espoo Finland      --