| 1 | <!DOCTYPE html>\r |
| 2 | <html lang="en">\r |
| 3 | <head>\r |
| 4 | <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">\r |
| 5 | <meta name="generator" content="AsciiDoc 8.6.9">\r |
| 6 | <title>RunningOnSparc</title>\r |
| 7 | <link rel="stylesheet" href="./asciidoc.css" type="text/css">\r |
| 8 | <link rel="stylesheet" href="./pygments.css" type="text/css">\r |
| 9 | \r |
| 10 | \r |
| 11 | <script type="text/javascript" src="./asciidoc.js"></script>\r |
| 12 | <script type="text/javascript">\r |
| 13 | /*<![CDATA[*/\r |
| 14 | asciidoc.install();\r |
| 15 | /*]]>*/\r |
| 16 | </script>\r |
| 17 | <link rel="stylesheet" href="./mlton.css" type="text/css">\r |
| 18 | </head>\r |
| 19 | <body class="article">\r |
| 20 | <div id="banner">\r |
| 21 | <div id="banner-home">\r |
| 22 | <a href="./Home">MLton 20180207</a>\r |
| 23 | </div>\r |
| 24 | </div>\r |
| 25 | <div id="header">\r |
| 26 | <h1>RunningOnSparc</h1>\r |
| 27 | </div>\r |
| 28 | <div id="content">\r |
| 29 | <div id="preamble">\r |
| 30 | <div class="sectionbody">\r |
| 31 | <div class="paragraph"><p>MLton runs fine on the Sparc architecture.</p></div>\r |
| 32 | </div>\r |
| 33 | </div>\r |
| 34 | <div class="sect1">\r |
| 35 | <h2 id="_notes">Notes</h2>\r |
| 36 | <div class="sectionbody">\r |
| 37 | <div class="ulist"><ul>\r |
| 38 | <li>\r |
| 39 | <p>\r |
| 40 | When compiling for Sparc, MLton targets the 32-bit Sparc\r |
| 41 | architecture (i.e., Sparc V8).\r |
| 42 | </p>\r |
| 43 | </li>\r |
| 44 | <li>\r |
| 45 | <p>\r |
| 46 | When compiling for Sparc, MLton doesn’t support native code\r |
| 47 | generation (<span class="monospaced">-codegen native</span>). Hence, performance is not as good as\r |
| 48 | it might be and compile times are longer. Also, the quality of code\r |
| 49 | generated by <span class="monospaced">gcc</span> is important. By default, MLton calls <span class="monospaced">gcc -O1</span>.\r |
| 50 | You can change this by calling MLton with <span class="monospaced">-cc-opt -O2</span>. We have seen\r |
| 51 | this speed up some programs by as much as 30%, especially those\r |
| 52 | involving floating point; however, it can also more than double\r |
| 53 | compile times.\r |
| 54 | </p>\r |
| 55 | </li>\r |
| 56 | <li>\r |
| 57 | <p>\r |
| 58 | When compiling for Sparc, MLton uses <span class="monospaced">-align 8</span> by default. While\r |
| 59 | this speeds up reals, it also may increase object sizes. If your\r |
| 60 | program does not make significant use of reals, you might see a\r |
| 61 | speedup with <span class="monospaced">-align 4</span>.\r |
| 62 | </p>\r |
| 63 | </li>\r |
| 64 | </ul></div>\r |
| 65 | </div>\r |
| 66 | </div>\r |
| 67 | <div class="sect1">\r |
| 68 | <h2 id="_known_issues">Known issues</h2>\r |
| 69 | <div class="sectionbody">\r |
| 70 | <div class="ulist"><ul>\r |
| 71 | <li>\r |
| 72 | <p>\r |
| 73 | Bootstrapping on the <a href="RunningOnSparc">Sparc architecture</a> is so slow\r |
| 74 | as to be impractical (many hours on a 500MHz UltraSparc). For this\r |
| 75 | reason, we strongly recommend building with a\r |
| 76 | <a href="CrossCompiling">cross compiler</a>.\r |
| 77 | </p>\r |
| 78 | </li>\r |
| 79 | </ul></div>\r |
| 80 | </div>\r |
| 81 | </div>\r |
| 82 | <div class="sect1">\r |
| 83 | <h2 id="_also_see">Also see</h2>\r |
| 84 | <div class="sectionbody">\r |
| 85 | <div class="ulist"><ul>\r |
| 86 | <li>\r |
| 87 | <p>\r |
| 88 | <a href="RunningOnSolaris">RunningOnSolaris</a>\r |
| 89 | </p>\r |
| 90 | </li>\r |
| 91 | </ul></div>\r |
| 92 | </div>\r |
| 93 | </div>\r |
| 94 | </div>\r |
| 95 | <div id="footnotes"><hr></div>\r |
| 96 | <div id="footer">\r |
| 97 | <div id="footer-text">\r |
| 98 | </div>\r |
| 99 | <div id="footer-badges">\r |
| 100 | </div>\r |
| 101 | </div>\r |
| 102 | </body>\r |
| 103 | </html>\r |