| Home | Libraries | People | FAQ | More

# Compiler Status

Will all boost libraries work with your compiler? Unfortunately, the answer is "it depends.".

Boost libraries rely on modern C++ features such as templates and the C++ Standard Library. Most modern compilers support those major features fairly well. But even today, years after the adoption of the C++ Standard, some compilers still don't support important minor features like partial template specialization.

Boost library authors often expend a great deal of effort trying to work around compiler deficiencies. Nevertheless, some libraries will not compile at all with certain compilers or may have crippled functionality. Even if the current release of a compiler supports a boost library, older version of the compiler may not work properly.

## Compiler Status Tables

- BeOS5/Intel [compiler messages] Contributed by John Maddock
- Compaq Tru64 Unix 5.0 [compiler messages] Contributed by Jens Maurer in co-operation with Ralf W. Grosse-Kunstleve
- HP/UX 10.x Contributed by Thomas Matelich
- Linux/x86 [compiler messages] Contributed by Jens Maurer
- Microsoft Windows NT / Windows 2000 [compiler messages] Contributed by Beman Dawes
- SGI IRIX 6.5 [compiler messages] Contributed by Jens Maurer in co-operation with Ralf W. Grosse-Kunstleve
- Sun Solaris/SPARC 2.7 [compiler messages] Contributed by Jens Maurer in co-operation with Andrew Lumsdaine

Boost releases are run through a regression test suite which automatically generates the above tables. Unless otherwise indicated, the C++ Standard Library implementation is the one shipped with the compiler.

Warning: These tables are not a good indication of a particular compiler's compliance with the C++ Standard. The boost libraries often contain workarounds which mask compiler deficiencies.

Warning: Some regression tests are compile only tests, or compile-and-link tests; the programs are not executed or otherwise tested. See the "Test Type" column in the tables. Even the compilation results may be spurious; many negative results stem from problems with the immature test suite rather that with the library or compiler. Furthermore, some library tests have not yet been included.

Revised 10 February 2001