Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!ames!amdcad!tim
From: tim@amdcad.UUCP
Newsgroups: comp.arch,comp.sys.nsc.32k
Subject: Re: Re: the NS32532
Message-ID: <16151@amdcad.AMD.COM>
Date: Tue, 14-Apr-87 20:05:09 EST
Article-I.D.: amdcad.16151
Posted: Tue Apr 14 20:05:09 1987
Date-Received: Thu, 16-Apr-87 00:32:30 EST
References: <4190@nsc.nsc.com> <951@moscom.UUCP> <2577@intelca.UUCP> <219@homxb.UUCP>
Reply-To: tim@amdcad.UUCP (Tim Olson)
Organization: Advanced Micro Devices, Inc., Sunnyvale, Ca.
Lines: 20
Xref: utgpu comp.arch:870 comp.sys.nsc.32k:65

In article <219@homxb.UUCP> gemini@homxb.UUCP (Rick Richardson) writes:
>                               ...  Meanwhile, any advice on modifying
>the Dhrystone for version 1.2 such that a global optimizer won't be
>able to remove anything will be appreciated.

One easy fix to Dhrystone is to package it as two (or more) separate c
files which must be compiled separately, then linked together.  This
will prevent global optimizers from looking at the entire program at one
whack, and is much more realistic (i.e.  most real-life programs are
made up of many files.) One question would be how to partition the
procedures and data declarations over multiple files realistically.  I
myself tend to use an "object oriented" approach, where data
declarations and the procedures to operate on said data exist in their
own file, and the data declarations tend to be "static" -- only visible
to the procedures within that file. 

	-- Tim Olson
	Advanced Micro Devices
	(tim@amdcad.AMD.COM)