4 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
5 <meta name="generator" content="AsciiDoc 8.6.9">
6 <title>RunningOnAMD64</title>
7 <link rel="stylesheet" href="./asciidoc.css" type="text/css">
8 <link rel="stylesheet" href="./pygments.css" type="text/css">
11 <script type="text/javascript" src="./asciidoc.js"></script>
12 <script type="text/javascript">
17 <link rel="stylesheet" href="./mlton.css" type="text/css">
19 <body class="article">
21 <div id="banner-home">
22 <a href="./Home">MLton 20180207</a>
26 <h1>RunningOnAMD64</h1>
30 <div class="sectionbody">
31 <div class="paragraph"><p>MLton runs fine on the AMD64 (aka "x86-64" or "x64") architecture.</p></div>
35 <h2 id="_notes">Notes</h2>
36 <div class="sectionbody">
37 <div class="ulist"><ul>
40 When compiling for AMD64, MLton targets the 64-bit ABI.
45 On AMD64, MLton supports native code generation (<span class="monospaced">-codegen native</span> or <span class="monospaced">-codegen amd64</span>).
50 When compiling for AMD64, MLton uses <span class="monospaced">-align 8</span> by default. Using
51 <span class="monospaced">-align 4</span> may be incompatible with optimized builds of the <a href="GnuMP">GnuMP</a>
52 library, which assume 8-byte alignment. (See the thread at
53 <a href="http://www.mlton.org/pipermail/mlton/2009-October/030674.html">http://www.mlton.org/pipermail/mlton/2009-October/030674.html</a> for more
61 <div id="footnotes"><hr></div>
63 <div id="footer-text">
65 <div id="footer-badges">