Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!wuarchive!sdd.hp.com!mips!cs.uoregon.edu!ogicse!intelhf!ichips!inews!bishop!bhoughto
From: bhoughto@bishop.intel.com (Blair P. Houghton)
Newsgroups: comp.lang.c
Subject: Re: low level optimization
Message-ID: <3905@inews.intel.com>
Date: 19 Apr 91 03:54:09 GMT
References: <21703@lanl.gov> <1991Apr18.124836.5686@watmath.waterloo.edu> <21818@lanl.gov>
Sender: news@inews.intel.com
Organization: Intel Corp, Chandler, AZ
Lines: 17

In article <21818@lanl.gov> jlg@cochiti.lanl.gov (Jim Giles) writes:
>Note: the standard specifically says that files may be compiled
>in any order and that the only standard communication between files
>is through external variables and functions.

They sure may, but why is it so horrible to you to document
to the users of your optimized libraries that certain
arguments to certain functions must be carefully
non-aliased?  That kind of restriction stopped nobody from
specifying a standard function that defines and returns a
static object (thus making more than one call to the
function a risky construct, at best...)

				--Blair
				  "How does Yogi eat all that
				   honey right out of the tree
				   without getting stung?"