<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="generator" content="AsciiDoc 8.6.8">
<title>RunningOnIA64</title>
<link rel="stylesheet" href="./asciidoc.css" type="text/css">
<link rel="stylesheet" href="./pygments.css" type="text/css">


<script type="text/javascript" src="./asciidoc.js"></script>
<script type="text/javascript">
/*<![CDATA[*/
asciidoc.install();
/*]]>*/
</script>
<link rel="stylesheet" href="./mlton.css" type="text/css"/>
</head>
<body class="article">
<div id="banner">
<div id="banner-home">
<a href="./Home">MLton 20130715</a>
</div>
</div>
<div id="header">
<h1>RunningOnIA64</h1>
</div>
<div id="content">
<div id="preamble">
<div class="sectionbody">
<div class="paragraph"><p>MLton runs fine on the IA64 architecture.</p></div>
</div>
</div>
<div class="sect1">
<h2 id="_notes">Notes</h2>
<div class="sectionbody">
<div class="ulist"><ul>
<li>
<p>
When compiling for IA64, MLton targets the 64-bit ABI.
</p>
</li>
<li>
<p>
When compiling for IA64, MLton doesn&#8217;t support native code
generation (<span class="monospaced">-codegen native</span>).  Hence, performance is not as good as
it might be and compile times are longer.  Also, the quality of code
generated by <span class="monospaced">gcc</span> is important.  By default, MLton calls <span class="monospaced">gcc -O1</span>.
You can change this by calling MLton with <span class="monospaced">-cc-opt -O2</span>.
</p>
</li>
<li>
<p>
When compiling for IA64, MLton uses <span class="monospaced">-align 8</span> by default.
</p>
</li>
<li>
<p>
On the IA64, the <a href="GnuMP">GnuMP</a> library supports multiple ABIs.  See the
<a href="GnuMP">GnuMP</a> page for more details.
</p>
</li>
</ul></div>
</div>
</div>
</div>
<div id="footnotes"><hr></div>
<div id="footer">
<div id="footer-text">
</div>
<div id="footer-badges">
</div>
</div>
</body>
</html>
