doc/guide/localhost/RunningOnARM

   1 <!DOCTYPE html>
   2 <html lang="en">
   3 <head>
   4 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
   5 <meta name="generator" content="AsciiDoc 8.6.9">
   6 <title>RunningOnARM</title>
   7 <link rel="stylesheet" href="./asciidoc.css" type="text/css">
   8 <link rel="stylesheet" href="./pygments.css" type="text/css">
   9
  10
  11 <script type="text/javascript" src="./asciidoc.js"></script>
  12 <script type="text/javascript">
  13 /*<![CDATA[*/
  14 asciidoc.install();
  15 /*]]>*/
  16 </script>
  17 <link rel="stylesheet" href="./mlton.css" type="text/css">
  18 </head>
  19 <body class="article">
  20 <div id="banner">
  21 <div id="banner-home">
  22 <a href="./Home">MLton 20180207</a>
  23 </div>
  24 </div>
  25 <div id="header">
  26 <h1>RunningOnARM</h1>
  27 </div>
  28 <div id="content">
  29 <div id="preamble">
  30 <div class="sectionbody">
  31 <div class="paragraph"><p>MLton runs fine on the ARM architecture.</p></div>
  32 </div>
  33 </div>
  34 <div class="sect1">
  35 <h2 id="_notes">Notes</h2>
  36 <div class="sectionbody">
  37 <div class="ulist"><ul>
  38 <li>
  39 <p>
  40 When compiling for ARM, MLton doesn&#8217;t support native code generation
  41 (<span class="monospaced">-codegen native</span>).  Hence, performance is not as good as it might be
  42 and compile times are longer.  Also, the quality of code generated by
  43 <span class="monospaced">gcc</span> is important.  By default, MLton calls <span class="monospaced">gcc -O1</span>.  You can
  44 change this by calling MLton with <span class="monospaced">-cc-opt -O2</span>.
  45 </p>
  46 </li>
  47 </ul></div>
  48 </div>
  49 </div>
  50 </div>
  51 <div id="footnotes"><hr></div>
  52 <div id="footer">
  53 <div id="footer-text">
  54 </div>
  55 <div id="footer-badges">
  56 </div>
  57 </div>
  58 </body>
  59 </html>