Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!batcomputer!cornell!uw-beaver!rice!hsdndev!cmcl2!lanl!cochiti.lanl.gov!jlg
From: jlg@cochiti.lanl.gov (Jim Giles)
Newsgroups: comp.lang.c
Subject: Re: low level optimization
Message-ID: <23103@lanl.gov>
Date: 2 May 91 21:39:25 GMT
References: <22687@lanl.gov> <4037@bruce.cs.monash.OZ.AU> <22841@lanl.gov> <1991May02.173643.9528@kithrup.COM>
Sender: news@lanl.gov
Organization: Los Alamos National Laboratory
Lines: 13

In article <1991May02.173643.9528@kithrup.COM>, sef@kithrup.COM (Sean Eric Fagan) writes:
|> [...]
|> The unix linker is, essentially, part of the "translation" process for C on
|> unix.  So there is no "post-translation" optimisation.

You need to read your copy of the standard more carefully.  The C standard
_specifically_ make a distinction between translation and linking.  Source
'files' may be 'translated' in any order and separately and subsequently
'linked' together to form a program.  Define these terms how you like, 
but don't expect any vendors to agree with you.  In the meantime, what
the standard has in mind is perfectly clear: separate compilation.

J. Giles