forked from OctaForge/libostd
bump gcc requirement to 5.4+/6+ as i'm tired of dealing with ICEs and standards compliance issues
This commit is contained in:
parent
b7a2322990
commit
826c28ab36
|
@ -11,7 +11,7 @@ Full C++14 support is required in your compiler.
|
||||||
|
|
||||||
Compiler | Version
|
Compiler | Version
|
||||||
-------- | -------
|
-------- | -------
|
||||||
gcc/g++ | 5+
|
gcc/g++ | 5.4+, 6+
|
||||||
clang | 3.8+
|
clang | 3.8+
|
||||||
|
|
||||||
Other C++14 compliant compilers might work as well. OctaSTD does not utilize
|
Other C++14 compliant compilers might work as well. OctaSTD does not utilize
|
||||||
|
@ -27,6 +27,12 @@ from a bug in its template variable implementation that prevents OctaSTD from
|
||||||
functioning. Therefore version 3.8 or higher is necessary (where this bug was
|
functioning. Therefore version 3.8 or higher is necessary (where this bug was
|
||||||
finally fixed).
|
finally fixed).
|
||||||
|
|
||||||
|
GCC has implemented a sufficient feature level of C++14 since version 5.1, but
|
||||||
|
also is too buggy until version 5.4. Version 5.1 and 5.2 have template variable
|
||||||
|
partial specialization issues and version 5.3 has an internal compiler error
|
||||||
|
triggered by the tuple implementation. Version 5.4 appears to be the first one
|
||||||
|
to compile this without issues. GCC 6.1 also appears to compile without problems.
|
||||||
|
|
||||||
MSVC++ is currently unsupported. It is likely that it will never be supported,
|
MSVC++ is currently unsupported. It is likely that it will never be supported,
|
||||||
as MS recently introduced Clang frontend support in Visual Studio; however,
|
as MS recently introduced Clang frontend support in Visual Studio; however,
|
||||||
if their own frontend gains all the necessary features, support will be
|
if their own frontend gains all the necessary features, support will be
|
||||||
|
|
Loading…
Reference in a new issue