[type_traits] common_type errors with Oracle compiler
Hi,
Both oracle-intel-S2-next-cpp11 and oracle-sparc-S2-next-stlport4
testers fail to compile common_type as it is being used in Boost.Chrono.
This in turn affects compilation of Boost.Thread and multiple other
library tests. The error can be seen here:
http://www.boost.org/development/tests/develop/developer/output/oracle-intel...
Just in case if the test results go down, I'm copying the error inline
below. Could it be fixed?
"CC" -std=c++11 -temp=/tmp/bn -xO4 -mt -erroff=%none -m32 -KPIC
-DBOOST_ALL_NO_LIB=1 -DBOOST_ATOMIC_DYN_LINK=1 -DBOOST_CHRONO_DYN_LINK=1
-DBOOST_SYSTEM_DYN_LINK=1 -DBOOST_SYSTEM_NO_DEPRECATED
-DBOOST_THREAD_BUILD_DLL=1 -DBOOST_THREAD_POSIX -DBOOST_THREAD_USE_DLL=1
-DNDEBUG -D__typeof__=__typeof__ -I".." -c -o
"/export/home/sstrunk-tester/boost_regression/boost_regression_develop/boost_intel-S2_cpp11/results/boost/bin.v2/libs/atomic/test/atomicity.test/sun-next_cpp11/release/threading-multi/atomicity.o"
"../libs/atomic/test/atomicity.cpp"
"../boost/chrono/duration.hpp", line 405: Error: type is not a member of
boost::common_type
On 01/10/2015 11:59, Andrey Semashev wrote:
Hi,
Both oracle-intel-S2-next-cpp11 and oracle-sparc-S2-next-stlport4 testers fail to compile common_type as it is being used in Boost.Chrono. This in turn affects compilation of Boost.Thread and multiple other library tests. The error can be seen here:
http://www.boost.org/development/tests/develop/developer/output/oracle-intel...
Just in case if the test results go down, I'm copying the error inline below. Could it be fixed?
Not unless someone tells me how. Actually I'm not sure what compiler they're run against - config_info reports C++ version 5.14, but 5.13 is the latest I can find anywhere. Both the type_traits and chrono tests pass with 5.13 BTW. Maybe this is an as yet unreleased beta compiler? Confused yours, John.
On 01.10.2015 15:31, John Maddock wrote:
On 01/10/2015 11:59, Andrey Semashev wrote:
Hi,
Both oracle-intel-S2-next-cpp11 and oracle-sparc-S2-next-stlport4 testers fail to compile common_type as it is being used in Boost.Chrono. This in turn affects compilation of Boost.Thread and multiple other library tests. The error can be seen here:
http://www.boost.org/development/tests/develop/developer/output/oracle-intel...
Just in case if the test results go down, I'm copying the error inline below. Could it be fixed?
Not unless someone tells me how. Actually I'm not sure what compiler they're run against - config_info reports C++ version 5.14, but 5.13 is the latest I can find anywhere. Both the type_traits and chrono tests pass with 5.13 BTW.
Maybe this is an as yet unreleased beta compiler?
I'm not sure either. If it's an unreleased compiler then feel free to disregard my request.
On 01.10.2015 15:31, John Maddock wrote:
On 01/10/2015 11:59, Andrey Semashev wrote:
Hi,
Both oracle-intel-S2-next-cpp11 and oracle-sparc-S2-next-stlport4 testers fail to compile common_type as it is being used in Boost.Chrono. This in turn affects compilation of Boost.Thread and multiple other library tests. The error can be seen here:
http://www.boost.org/development/tests/develop/developer/output/oracle-intel...
Just in case if the test results go down, I'm copying the error inline below. Could it be fixed?
Not unless someone tells me how. Actually I'm not sure what compiler they're run against - config_info reports C++ version 5.14, but 5.13 is the latest I can find anywhere. Both the type_traits and chrono tests pass with 5.13 BTW.
Maybe this is an as yet unreleased beta compiler?
I'm not sure either. If it's an unreleased compiler then feel free to disregard my request. Yes, this is the internal development compiler. For purposes of this testing, C++11 features supported in this release have been turned in
On 10/01/15 07:41, Andrey Semashev wrote: the local workspace by modifying the sunpro_cc.hpp file. Thanks, Aparna
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
I'm not sure either. If it's an unreleased compiler then feel free to disregard my request. Yes, this is the internal development compiler. For purposes of this testing, C++11 features supported in this release have been turned in the local workspace by modifying the sunpro_cc.hpp file.
In that case, would it be possible to give the test runner for these a more descriptive name - something that clearly indicates the results are run on a beta (or alpha?) compiler release? Many thanks for confirmation though, John.
participants (3)
-
Andrey Semashev -
Aparna Kumta -
John Maddock