Download Red Hat Developer Toolset 2.x User Guide

Red Hat D eveloper Toolset 2.x User Guide
T he INT {8,16,32} and REAL{32,64 ,128} format for ISO_FORT RAN_ENV intrinsic module type
parameters are now supported.
It is now possible to use complex arguments with the T AN, SINH, COSH, T ANH, ASIN, ACOS, and
AT AN functions. Additionally, the new functions ASINH, ACOSH, and AT ANH have been added for real
and complex arguments, and AT AN(Y,X) now serves as an alias for AT AN2(Y,X).
T he BLOCK construct has been implemented.
A.2.2.2.4 .6. Fortran 2008 Compatibility
T he implementation of the ASYNCHRONOUS attribute in GCC is now compatible with the candidate draft
of TS 29113: Technical Specification on Further Interoperability with C.
A.2.2.2.4 .7. Fortran 77 Compatibility
When the GNU Fortran compiler is issued with the -fno-sign-zero option, the SIGN intrinsic now
behaves as if zero were always positive.
A.2.2.3. ABI Compatibility
T his section describes compatibility between the Red Hat Developer T oolset compilers and the system
compilers at the application binary interface (ABI) level.
A.2.2.3.1. C++ ABI
Because the upstream GCC community development does not guarantee C++11 ABI compatibility
across major versions of GCC, the same applies to use of C++11 with Red Hat Developer T oolset.
Consequently, using the -std=c++11 option is supported in Red Hat Developer T oolset 2.0 only when
all C++ objects compiled with that flag have been built using the same major version of Red Hat
Developer T oolset. T he mixing of objects, binaries and libraries, built by the Red Hat Enterprise Linux 5
or 6 system toolchain GCC using the -std=c++0x or -std=gnu++0x flags, with those built with the std=c++11 or -std=gnu++11 flags using the GCC in Red Hat Developer T oolset is explicitly not
supported.
As later major versions of Red Hat Developer T oolset may use a later major release of GCC, forwardcompatibility of objects, binaries, and libraries built with the -std=c++11 or -std=gnu++11 options
cannot be guaranteed, and so is not supported.
T he default language standard setting for Red Hat Developer T oolset is C++98. Any C++98-compliant
binaries or libraries built in this default mode (or explicitly with -std=c++98) can be freely mixed with
binaries and shared libraries built by the Red Hat Enterprise Linux 5 or 6 system toolchain GCC. Red
Hat recommends use of this default -std=c++98 mode for production software development.
Important
Use of C++11 features in your application requires careful consideration of the above ABI
compatibility information.
Aside from the C++11 ABI, discussed above, the Red Hat Enterprise Linux Application Compatibility
Specification is unchanged for Red Hat Developer T oolset. When mixing objects built with Red Hat
Developer T oolset with those built with the Red Hat Enterprise Linux v5.x/v6.x toolchain (particularly .o/.a
files), the Red Hat Developer T oolset toolchain should be used for any linkage. T his ensures any newer
library features provided only by Red Hat Developer T oolset are resolved at link-time.
A new standard mangling for SIMD vector types has been added to avoid name clashes on systems with
114