compiler_status.html 10.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280
  1. <html>
  2. <head>
  3. <meta http-equiv="Content-Type"
  4. content="text/html; charset=iso-8859-1">
  5. <meta name="ProgId" content="FrontPage.Editor.Document">
  6. <meta name="GENERATOR" content="Microsoft FrontPage 4.0">
  7. <title>Boost Compiler Status Report</title>
  8. </head>
  9. <body bgcolor="#FFFFFF" text="#000000">
  10. <table border="1" bgcolor="#007F7F" cellpadding="2">
  11. <tr>
  12. <td bgcolor="#FFFFFF"><img src="../c++boost.gif" alt="c++boost.gif (8819 bytes)" width="277" height="86"></td>
  13. <td><a href="../index.htm"><font face="Arial" color="#FFFFFF"><big>Home</big></font></a></td>
  14. <td><a href="../libs/libraries.htm"><font face="Arial" color="#FFFFFF"><big>Libraries</big></font></a></td>
  15. <td><a href="../people/people.htm"><font face="Arial" color="#FFFFFF"><big>People</big></font></a></td>
  16. <td><a href="../more/faq.htm"><font face="Arial" color="#FFFFFF"><big>FAQ</big></font></a></td>
  17. <td><a href="../more/index.htm"><font face="Arial" color="#FFFFFF"><big>More</big></font></a></td>
  18. </tr>
  19. </table>
  20. <h1>Compiler Status</h1>
  21. <p><a href="#Introduction">Introduction</a><br>
  22. <a href="#Tables">Compiler Status Tables</a><br>
  23. <a href="#Understanding">Understanding the Tables</a><br>
  24. <a href="#Acknowledgements">Acknowledgements</a></p>
  25. <h2><a name="Introduction">Introduction</a></h2>
  26. <p>Will all boost libraries work with your compiler?&nbsp;
  27. Unfortunately, the answer is &quot;it depends.&quot;.</p>
  28. <p>Boost libraries rely on modern C++ features such as templates
  29. and the C++ Standard Library.&nbsp; Most modern compilers support those major
  30. features fairly well. But even today, years after
  31. the adoption of the C++ Standard, some compilers still don't
  32. support important minor features like partial template specialization.</p>
  33. <p>Boost library authors often expend a great deal of effort
  34. trying to work around compiler deficiencies.&nbsp; Nevertheless,
  35. some libraries will not compile at all with certain compilers or
  36. may have crippled functionality.&nbsp; Even if the current
  37. release of a compiler supports a boost library, older versions of
  38. the compiler may not work properly.</p>
  39. <p>Boost releases are run through a <a href="../more/regression.html">regression test
  40. suite</a> which
  41. automatically generates Compiler Status Tables for various platforms. Unless otherwise
  42. indicated, the C++ Standard Library implementation is the one
  43. shipped with the compiler.</p>
  44. <h2>Compiler Status <a name="Tables"> Tables</a></h2>
  45. <p><b>Warning:</b> These tables are not a good indication of a
  46. particular compiler's compliance with the C++ Standard.&nbsp; The Boost libraries often contain workarounds which mask compiler
  47. deficiencies.</p>
  48. <table border="1" cellpadding="5" cellSpacing="0">
  49. <tr>
  50. <td><b>Link to<br>
  51. Compiler Status Table<br>
  52. </b></td>
  53. <td><b>Link to<br>
  54. Regression<br>
  55. Test messages</b></td>
  56. <td><b>Contributed by</b></td>
  57. </tr>
  58. <tr>
  59. <td><a href="cs-macosx.html">Apple Mac OS X</a> </td>
  60. <td><a href="http://boost.sourceforge.net/regression-logs/macosx.log.gz">messages</a>
  61. </td>
  62. <td><a href="../people/darin_adler.htm">Darin Adler</a></td>
  63. </tr>
  64. <tr>
  65. <td><a href="cs-beos.html">BeOS5 Intel</a> </td>
  66. <td><a href="http://boost.sourceforge.net/regression-logs/beos.log.gz">messages</a>
  67. </td>
  68. <td><a href="../people/john_maddock.htm">John Maddock</a></td>
  69. </tr>
  70. <tr>
  71. <td><a href="cs-tru64.html">Compaq Tru64 Unix 5.0</a> </td>
  72. <td><a href="http://boost.sourceforge.net/regression-logs/alpha.log.gz">messages</a>
  73. </td>
  74. <td><a href="../people/jens_maurer.htm">Jens Maurer</a>
  75. in cooperation with
  76. <a href="../people/ralf_w_grosse_kunstleve.htm">Ralf W. Grosse-Kunstleve</a>
  77. </td>
  78. </tr>
  79. <tr>
  80. <td><a href="cs-hpux.html">HP/UX 11.0</a> </td>
  81. <td><a href="http://boost.sourceforge.net/regression-logs/hpux.log.gz">messages</a>
  82. </td>
  83. <td><a href="../people/jens_maurer.htm">Jens Maurer</a>
  84. in cooperation with Thomas Matelich and Hewlett-Packard</td>
  85. </tr>
  86. <tr>
  87. <td><a href="cs-aix.html">IBM Aix</a> </td>
  88. <td><a href="http://boost.sourceforge.net/regression-logs/aix.log.gz">messages</a>
  89. </td>
  90. <td> Toon Knapen</td>
  91. </tr>
  92. <tr>
  93. <td><a href="cs-linux.html">Linux x86</a> </td>
  94. <td><a href="http://boost.sourceforge.net/regression-logs/linux.log.gz">messages</a>
  95. </td>
  96. <td><a href="../people/jens_maurer.htm">Jens Maurer</a></td>
  97. </tr>
  98. <tr>
  99. <td><a href="cs-win32.html">Microsoft Windows 2000</a> </td>
  100. <td><a href="http://boost.sourceforge.net/regression-logs/win32.zip">messages</a>
  101. </td>
  102. <td><a href="../people/beman_dawes.html">Beman Dawes</a></td>
  103. </tr>
  104. <tr>
  105. <td><a href="cs-irix.html">SGI IRIX 6.5</a> </td>
  106. <td><a href="http://boost.sourceforge.net/regression-logs/irix.log.gz">messages</a>
  107. </td>
  108. <td><a href="../people/jens_maurer.htm">Jens Maurer</a>
  109. in cooperation with
  110. <a href="../people/ralf_w_grosse_kunstleve.htm">Ralf W. Grosse-Kunstleve</a>
  111. </td>
  112. </tr>
  113. <tr>
  114. <td><a href="cs-solaris.html">Sun Solaris SPARC 2.8</a> </td>
  115. <td><a href="http://boost.sourceforge.net/regression-logs/solaris.log.gz">messages</a>
  116. </td>
  117. <td><a href="../people/jens_maurer.htm">Jens Maurer</a>
  118. in cooperation with Andrew Lumsdaine</td>
  119. </tr>
  120. </table>
  121. <h2><a name="Understanding">Understanding</a> the Tables</h2>
  122. <p>A table might look like this:</p>
  123. <blockquote>
  124. <p><b>Run Date:</b> 21 Sep 2001 15:31 GMT</p>
  125. <p><b>System Configuration:</b> Microsoft Windows 32bit</p>
  126. <p>&nbsp;
  127. <table border="1" cellPadding="5" cellSpacing="0">
  128. <tbody>
  129. <tr>
  130. <td>Program</td>
  131. <td>Test<br>
  132. Type</td>
  133. <td>BelchFire<br>
  134. Rev 5280</td>
  135. <td>WorkHorse<br>
  136. 5.3</td>
  137. </tr>
  138. <tr>
  139. <td>libs/foo/test/foo_test.cpp</td>
  140. <td>compile</td>
  141. <td>Pass</td>
  142. <td>Pass</td>
  143. </tr>
  144. <tr>
  145. <td>libs/bar/bar_test.cpp</td>
  146. <td>run</td>
  147. <td><font color="#ff0000">Fail</font></td>
  148. <td>Pass</td>
  149. </tr>
  150. </tbody>
  151. </table>
  152. </blockquote>
  153. <p>The <i>Run Date</i> is important because the regression tests which create
  154. the status tables are run asynchronously, and thus may not represent the most
  155. current Boost release.</p>
  156. <p>The <i>Program</i> column identifies the actual source file for the
  157. test.&nbsp; Each row in the table represents a different test.</p>
  158. <p>The <i>Test Type</i> column identifies the type of test performed:</p>
  159. <table border="1" cellpadding="5" cellSpacing="0">
  160. <tr>
  161. <td><b>Test Type</b></td>
  162. <td><b>Action</b></td>
  163. <td><b>Required to <i>Pass</i></b></td>
  164. <td><b>Description and Use</b></td>
  165. </tr>
  166. <tr>
  167. <td>compile</td>
  168. <td>compile only</td>
  169. <td>Compiler returns 0.</td>
  170. <td>Verify that a source file will compile correctly, but without any
  171. attempt to link or execute.&nbsp; Used when factors such as possible
  172. object library unavailability make a run test impractical.</td>
  173. </tr>
  174. <tr>
  175. <td>compile-fail</td>
  176. <td>compile only</td>
  177. <td>Compiler must return non-zero.</td>
  178. <td>Verify that a source file fails to compile. Used to verify that an
  179. expected compile-time error was detected.</td>
  180. </tr>
  181. <tr>
  182. <td>link</td>
  183. <td>compile, link</td>
  184. <td>Both compiler &amp; linker return 0.</td>
  185. <td>Verify that a source file will compile and link correctly, but without
  186. any attempt to execute the result.&nbsp; Used when factors such as
  187. possible data file unavailability make a run test impractical.</td>
  188. </tr>
  189. <tr>
  190. <td>link-fail</td>
  191. <td>compile, link</td>
  192. <td>Either the compiler or linker must return non-zero.</td>
  193. <td>Verify that a source file fails to compile and link. Used to verify that
  194. error detect which depends on unresolved externals works correctly.</td>
  195. </tr>
  196. <tr>
  197. <td>run</td>
  198. <td>compile, link, execute</td>
  199. <td>Compiler, linker, and executable must all return 0.</td>
  200. <td>Verify that a source file compiles, links, and the resulting program
  201. executes correctly (as indicated by a zero return code.)&nbsp; This is the
  202. primary test type for most uses.</td>
  203. </tr>
  204. <tr>
  205. <td>run-fail</td>
  206. <td>compile, link, execute</td>
  207. <td>Both compiler and linker must return 0, and the executable must return
  208. non-zero.</td>
  209. <td>Verify that a source file compiles and links correctly, and that
  210. execution of the resulting program detects some error.&nbsp; Used to
  211. verify runtime error detection code works properly.</td>
  212. </tr>
  213. </table>
  214. <p>Each remaining column in the table represents the individual compiler
  215. indicated. Unless otherwise
  216. indicated, the C++ Standard Library implementation is the one
  217. shipped with the compiler. A <i>Pass</i> entry indicates success for the
  218. indicated <i>Test Type</i>, while a <font color="#ff0000"><i>Fail</i></font>
  219. entry indicates failure. See <i>Required to Pass</i> in the above table for
  220. specifics.&nbsp;</p>
  221. <h2><a name="Acknowledgements">Acknowledgements</a></h2>
  222. The compiler status tables have been prepared with resources donated by a number of individuals, educational institutions, and
  223. companies. Boost would like to thank them for their support.
  224. <ul>
  225. <li><p><a href="http://www.intel.com/software/products"><img border="0" src="intel_logo.gif" align="center" width="72" height="36">Intel
  226. Corporation</a>, California, USA
  227. <li><a href="http://www.kai.com/"><img border="0" src="kai_logo.gif" align="center" width="60" height="25"> KAI Software</a>, Illinois, USA<br>
  228. </li>
  229. <li><p><a href="http://www.hp.com/">Hewlett-Packard Company</a>, USA</p></li>
  230. <li><p><a href="http://www.lbl.gov">Lawrence Berkeley National Laboratory</a>, California, USA</p></li>
  231. <li><p><a href="http://www.nd.edu/">University of Notre Dame</a>,
  232. Indiana, USA</p>
  233. </ul>
  234. <p>
  235. Note, however, that Boost does not endorse any product or service, nor
  236. does Boost guarantee that some or all of its libraries work with any
  237. of the products or services mentioned above.
  238. <hr>
  239. <p>Revised <!--webbot bot="Timestamp" s-type="EDITED"
  240. s-format="%d %B %Y" startspan -->30 September 2001<!--webbot bot="Timestamp" endspan i-checksum="39489" --></p>
  241. </body>
  242. </html>
粤ICP备19079148号