<html>
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
p
{margin-right:0cm;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman";}
span.E-mailStijl18
{font-family:Arial;
color:navy;}
@page Section1
{size:595.3pt 841.9pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=NL link=blue vlink=blue style='word-wrap: break-word;-webkit-nbsp-mode: space;
-webkit-line-break: after-white-space'>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'>Dear Larry,</span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'>Till now, I’ve not
really the discussion about the use of the makefile. I’m only running a
vax here, (OpenVMS 7.3) on my P4 2.8 Ghz, running WXP</span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'>And think that at least
is much faster than the old hardware.</span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'>Even I’ve never
compiled any module, however, I expect to get a alpha server ds-10 within this
year.</span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'>After that, I want to
move my vax environment to AXP and probably build my own binary. (since that’s
what I normally do on OpenVMS).</span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'>For that, I don’t
use MMS, be the freeware MMK (Madgoat make), which can handle a normal make
file (as well mms scripts).</span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'>In this case, compiling
will only compile the modified sources, but of course the linking will take
some time (I expect less than 10 seconds on the DS-10), because that AXP is
quite faster than the 64 bit machine from around 1995. So if you want to change
the code, “make” is the right way</span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'>Maybe you have the
possibility to upgrade to OpenVMS 7.3-2. This might speed up your system,
because that VMS version has many improvement made for the IA64 port of OpenVMS.</span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'> </span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'>Kind regards,</span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'> </span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'>Broer</span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'> </span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>Van:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
simh-bounces@trailing-edge.com [mailto:simh-bounces@trailing-edge.com] <b><span
style='font-weight:bold'>Namens </span></b>Larry Baker<br>
<b><span style='font-weight:bold'>Verzonden:</span></b> Friday 19 September
2008 21:25<br>
<b><span style='font-weight:bold'>Aan:</span></b> simh@trailing-edge.com<br>
<b><span style='font-weight:bold'>Onderwerp:</span></b> Re: [Simh] The new
Makefile</span></font></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> </span></font></p>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>I have not compared the SIMH V3.8 Makefile with the replacement
proposed by Philipp. I have converted the SIMH V3.4 descrip.mms file (the
OpenVMS equivalent of a Makefile) to a DCL command procedure (the OpenVMS
equivalent of a shell script or batch file), make.com, for compiling with DEC C
on OpenVMS/Alpha and OpenVMS/VAX. I compiled everything using our 333 MHz
AlphaServer 1000A 5/333 (OpenVMS V7.2-1) and MicroVAX 4000-100 (OpenVMS V6.2)
cluster. As you know, these are VERY slow computers compared to any
modern PC or Mac. I did not find the time it took to compile
objectionable. I liked that I could see everything that went into each
simulator in one command line.</span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> </span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>My experience is that I recompile the simulator I use (MicroVAX) maybe
once or twice when a new release looks interesting. I don't usually have
to do that more than once a year or two. I am not concerned with the time
that takes. I am concerned about the performance of the simulator.
My preference is to provide the compiler with every opportunity at
compile time to optimize the generated code, specifically, by aggressively
inlining procedures and, when that is not possible, by making full use of inter-procedural
optimizations (IPOs). My impression is that the practice of separately
compiling every module makes this more difficult, if not impossible, which
makes me favor the current Makefile method. Of course this assumes SIMH
benefits from inlining and IPOs. My bias, when choices have to be made,
is to prefer alternatives that make the SIMH executable run faster, even if
that increases the compilation time.</span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> </span></font></p>
<div apple-content-edited=true>
<div>
<p style='margin:0cm;margin-bottom:.0001pt'><font size=1 face=Helvetica><span
style='font-size:9.0pt;font-family:Helvetica'>Larry Baker</span></font></p>
<p style='margin:0cm;margin-bottom:.0001pt'><font size=1 face=Helvetica><span
style='font-size:9.0pt;font-family:Helvetica'>US Geological Survey</span></font></p>
<p style='margin:0cm;margin-bottom:.0001pt'><font size=1 face=Helvetica><span
style='font-size:9.0pt;font-family:Helvetica'>650-329-5608</span></font></p>
<p style='margin:0cm;margin-bottom:.0001pt'><font size=1 face=Helvetica><span
style='font-size:9.0pt;font-family:Helvetica'><a href="mailto:baker@usgs.gov">baker@usgs.gov</a></span></font></p>
</div>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> </span></font></p>
</div>
</div>
</body>
</html>