Chapter 2.  Red Hat Developer Toolset 6.0 Release

This chapter serves as an overview of Red Hat Developer Toolset 6.0. It sums up its main features and changes, and provides a list of known issues.

2.1. Changes in Red Hat Developer Toolset 6.0

2.1.1. Upgraded Components

All components in Red Hat Developer Toolset 6.0 are shipped with the devtoolset-6- prefix.
Red Hat Developer Toolset 6.0 includes a new component, make 4.1, a tool for controlling the generation of executables and other non-source files of a program from the program's source files.
The following components have been upgraded in Red Hat Developer Toolset 6.0 compared to the previous release of Red Hat Developer Toolset:
  • GCC to version 6.2.1
  • binutils to version 2.27
  • elfutils to version 0.167
  • GDB to version 7.12
  • strace to version 4.12
  • SystemTap to version 3.0
  • Valgrind to version 3.12.0
  • Dyninst to version 9.2.0
For detailed information on changes in Red Hat Developer Toolset 6.0, see Red Hat Developer Toolset User Guide.

Note

The Eclipse component is now shipped as a separate rh-eclipse46 Software Collection for Red Hat Enterprise Linux 7. For details, see the Red Hat Software Collections Release Notes.

2.1.2. Container Images

Red Hat Developer Toolset 6.0 includes two pre-built docker-formatted container images:
  • The rhscl/devtoolset-6-toolchain-rhel7 image, which contains the following Red Hat Developer Toolset components:
    • devtoolset-6-gcc
    • devtoolset-6-gcc-c++
    • devtoolset-6-gcc-fortran
    • devtoolset-6-gdb
  • The rhscl/devtoolset-6-perftools-rhel7 image, which contains the following components:
    • devtoolset-6-oprofile
    • devtoolset-6-systemtap
    • devtoolset-6-valgrind
    • devtoolset-6-dyninst
    • devtoolset-6-elfutils
The container images are available from the Red Hat Container Registry. For details on how to obtain the images and how to run Red Hat Developer Toolset components using these images, see Red Hat Developer Toolset User Guide.

2.2. Features

2.2.1. List of Components

Red Hat Developer Toolset 6.0 provides the following components:

Development Tools

  • GNU Compiler Collection (GCC)
  • binutils
  • elfutils
  • dwz
  • make

Debugging Tools

  • GNU Debugger (GDB)
  • strace
  • ltrace
  • memstomp

Performance Monitoring Tools

  • SystemTap
  • Valgrind
  • OProfile
  • Dyninst
For details, see the Red Hat Developer Toolset Components table in the Red Hat Developer Toolset User Guide.

2.2.2. Main Features

The Red Hat Developer Toolset version of the GNU Compiler Collection (GCC) has been upgraded to version 6.2.1 with major improvements and many bug fixes.
The version of the GNU Debugger (GDB) included in Red Hat Developer Toolset provides new features, including the following:
  • Support for recording btrace without maintaining an active GDB connection.
  • Support for running interpreters on specified input or output devices.
The Red Hat Developer Toolset 6.0 version of binutils provides these features:
  • Support has been added for generating and using compressed debug sections.
  • The linker now automatically enables the read-only run-time relocations unless explicitly told otherwise. This helps to enhance the security of executables.
  • The assembler now supports the ARM v8.1 and ARM v8-M architectures, including the Adv.SIMD, LOR, PAN, Security, and DSP extensions.
For a full list of changes and features introduced in this release, see Red Hat Developer Toolset User Guide.

2.3. Known Issues

oprofile component
OProfile 1.1.0 shipped in Red Hat Developer Toolset 6.0 works on all supported architectures, with the exception of IBM z Systems, where only the ocount tool works on the following models: z196, zEC12, and z13. operf and the other tools, such as oparchive or opannotate, do not work on IBM z Systems. For profiling purposes, users are recommended to use the Red Hat Enterprise Linux 7 system OProfile 0.9.9 version, which supports opcontrol with TIMER software interrupts.
Note that for correct reporting of data collected by OProfile 0.9.9, the corresponding opreport utility is necessary. Thus opcontrol-based profiling should be performed with Red Hat Developer Toolset disabled because the reporting tools from Red Hat Developer Toolset cannot process data collected within opcontrol legacy mode correctly.
gcc component
The libatomic library is unavailable for the 64-bit ARM architecture on Red Hat Enterprise Linux 7.2 and earlier versions. As a consequence, the devtoolset-6-libatomic-devel package cannot be installed on such systems. In Red Hat Enterprise Linux 7.3, the libatomic package for the 64-bit ARM architecture is shipped in the gcc-libraries package.
gcc component
Under certain circumstances, the source RPM package for GCC (devtoolset-6-gcc.src.rpm) cannot be rebuilt on Red Hat Enterprise Linux 6 or Red Hat Enterprise Linux 7.
ltrace component
Under certain circumstances, the source RPM package for ltrace (devtoolset-6-ltrace.src.rpm) cannot be rebuilt.
systemtap component
The source RPM package for SystemTap (devtoolset-6-systemtap.src.rpm) cannot be rebuilt on Red Hat Enterprise Linux 6.
multiple components
The devtoolset-6-package_name-debuginfo packages can conflict with the corresponding packages from the base Red Hat Enterprise Linux system or from other versions of Red Hat Developer Toolset. This namely applies to devtoolset-6-gcc-debuginfo, devtoolset-6-ltrace-debuginfo, devtoolset-6-valgrind-debuginfo, and might apply to other debuginfo packages, too. A similar conflict can also occur in a multilib environment, where 64-bit debuginfo packages conflict with 32-bit debuginfo packages.
For example, on Red Hat Enterprise Linux 7, devtoolset-6-gcc-debuginfo conflicts with three packages: gcc-base-debuginfo, gcc-debuginfo, and gcc-libraries-debuginfo. On Red Hat Enterprise Linux 6, devtoolset-6-gcc-debuginfo conflicts with one package: gcc-libraries-debuginfo. As a consequence, if conflicting debuginfo packages are installed, attempts to install Red Hat Developer Toolset 6.0 can fail with a transaction check error message similar to the following examples:
file /usr/lib/debug/usr/lib64/libitm.so.1.0.0.debug from install of gcc-base-debuginfo-4.8.3-9.el7.x86_64 conflicts with file from package devtoolset-6-gcc-debuginfo-6.2.1-2.el7.x86_64
file /usr/lib/debug/usr/lib64/libtsan.so.0.0.0.debug from install of gcc-debuginfo-4.8.3-9.el7.x86_64 conflicts with file from package devtoolset-6-gcc-debuginfo-6.2.1-2.el7.x86_64
file /usr/src/debug/gcc-5.2.1-20150716/obj-x86_64-redhat-linux/x86_64-redhat-linux/libstdc++-v3/include/x86_64-redhat-linux/bits/c++config.h from install of gcc-libraries-debuginfo-5.2.1-2.1.el7.x86_64 conflicts with file from package devtoolset-6-gcc-debuginfo-6.2.1-2.el7.x86_64
file /usr/lib/debug/usr/lib64/libcilkrts.so.5.0.0.debug from install of gcc-libraries-debuginfo-4.9.0-6.1.1.el6.x86_64 conflicts with file from package devtoolset-6-gcc-debuginfo-6.2.1-2.el7.x86_64
To work around the problem, manually uninstall the conflicting debuginfo packages prior to installing Red Hat Developer Toolset 6.0. It is advisable to install only the relevant debuginfo packages when necessary and expect such problems to happen.
valgrind component, BZ#869184
The default Valgrind gdbserver support (--vgdb=yes) can cause certain register and flags values to be not always up-to-date due to optimizations done by the Valgrind core. The GDB utility is therefore unable to show certain parameters or variables of programs running under Valgrind. To work around this problem, use the --vgdb=full parameter. Note that programs might run slower under Valgrind when this parameter is used.
valgrind component, BZ#990931
Valgrind must be rebuilt without Red Hat Developer Toolset's GCC installed, or it will be used in preference to Red Hat Enterprise Linux system GCC. The binary files shipped by Red Hat are build using the system GCC. For any testing, Red Hat Developer Toolset's GDB should be used.

Other Notes

  • Red Hat Developer Toolset primarily aims to provide a compiler for development of user applications for deployment on multiple versions of Red Hat Enterprise Linux. Operating system components, kernel modules and device drivers generally correspond to a specific version of Red Hat Enterprise Linux, for which the supplied base OS compiler is recommended.
  • Red Hat Developer Toolset 6.0 supports only C, C++ and Fortran development. For other languages, invoke the system version of GCC available on Red Hat Enterprise Linux.
  • Building an application with Red Hat Developer Toolset 6.0 on Red Hat Enterprise Linux (for example, Red Hat Enterprise Linux 7) and then executing that application on an earlier minor version (such as Red Hat Enterprise Linux 6.6.z) may result in runtime errors due to differences in non-toolchain components between Red Hat Enterprise Linux releases. Users are advised to check compatibility carefully. Red Hat supports only execution of an application built with Red Hat Developer Toolset on the same, or a later, supported release of Red Hat Enterprise Linux than the version used to build that application.
  • All code in the non-shared library libstdc++_nonshared.a in Red Hat Developer Toolset 6.0 is licensed under the GNU General Public License v3 with additional permissions granted under Section 7, described in the GCC Runtime Library Exception version 3.1, as published by the Free Software Foundation.
  • The compiler included in Red Hat Developer Toolset emits newer DWARF debugging records than previous compilers available on Red Hat Enterprise Linux. These new debugging records improve the debugging experience in a variety of ways, particularly for C++ and optimized code. However, certain tools are not yet capable of handling the newer DWARF debug records. To generate the older style debugging records, use the options -gdwarf-2 -gstrict-dwarf or -gdwarf-3 -gstrict-dwarf.
  • Some newer library features are statically linked into applications built with Red Hat Developer Toolset to support execution on multiple versions of Red Hat Enterprise Linux. This adds a small additional security risk because regular Red Hat Enterprise Linux errata would not change this code. If the need for developers to rebuild their applications due to such an issue arises, Red Hat will signal this in a security erratum. Developers are strongly advised not to statically link their entire application for the same reasons.
  • Note that error messages related to a missing libitm library when using the -fgnu-tm option require the libitm package to be installed. You can install the package with the following command:
    yum install libitm
  • To use the ccache utility with GCC included in Red Hat Developer Toolset, set your environment correctly. For example:
    ~]$ scl enable devtoolset-6 '/usr/lib64/ccache/gcc -c foo.c'
    Alternatively, you can create a shell with the Red Hat Developer Toolset version of GCC as the default compiler:
    ~]$ scl enable devtoolset-6 'bash'
    After you have created the shell, run the following two commands:
    ~]$ export PATH=/usr/lib64/ccache${PATH:+:${PATH}}
    ~]$ gcc -c foo.c
  • Because the elfutils libraries contained in Red Hat Developer Toolset 6.0 are linked to a client application statically, caution is advised when passing handles to libelf, libdw, and libasm data structures to external code and when passing handles received from external code to libelf, libdw, and libasm.
    Be especially careful when an external library, which is linked dynamically against the system version of elfutils, is passed a pointer to a structure that comes from the Red Hat Developer Toolset 6.0 version of elfutils (or vice versa).
    Generally, data structures used in the Red Hat Developer Toolset 6.0 version of elfutils are not compatible with the Red Hat Enterprise Linux system versions, and structures coming from one should never be touched by the other.
    In applications that use the Red Hat Developer Toolset 6.0 libraries, all code that was linked against the system version of the libraries should be recompiled against the libraries included in Red Hat Developer Toolset 6.0.
  • The elfutils EBL library, which is used internally by libdw, was amended not to open back ends dynamically. Instead, a selection of back ends is compiled in the library itself: Intel x86 (i386), AMD64 and Intel 64 (x86_64), Intel Itanium, and IBM z Systems. Some functionality may not be available if the client wishes to work with ELF files from architectures other than those mentioned above.
  • Some packages managed by the scl utility include privileged services that require sudo. The system sudo clears environment variables and so Red Hat Developer Toolset includes its own sudo shell script, wrapping scl enable. This script does not currently parse or pass normal sudo options, only sudo COMMAND ARGS .... In order to use the system version of sudo from within a Red Hat Developer Toolset-enabled shell, use the /usr/bin/sudo binary.
  • Red Hat Developer Toolset 6.0 includes GCC 6.2, which provides support for Cilk+, an extension to the C and C++ languages for parallel programming. A runtime library, libcilkrts, is included in this release to support the feature. The libcilkrts library will be a part of the gcc-libraries package in the future Red Hat Enterprise Linux releases but the package is not included in all supported Red Hat Enterprise Linux releases. To enable dynamic linkage of binaries and libraries built with Red Hat Developer Toolset 6.0 GCC using Cilk+ features on supported Red Hat Enterprise Linux releases that do not contain libcilkrts, install the libcilkrts.so shared library from Red Hat Developer Toolset 6.0 with such binaries or libraries.
  • Intel have issued erratum HSW136 concerning TSX (Transactional Synchronization Extensions) instructions. Under certain circumstances, software using the Intel TSX instructions may result in unpredictable behavior. TSX instructions may be executed by applications built with Red Hat Developer Toolset GCC under certain conditions. These include use of GCC's experimental Transactional Memory support (using the -fgnu-tm option) when executed on hardware with TSX instructions enabled. The users of Red Hat Developer Toolset are advised to exercise further caution when experimenting with Transaction Memory at this time, or to disable TSX instructions by applying an appropriate hardware or firmware update.
  • To use the Memory Protection Extensions (MPX) feature in GCC, the Red Hat Developer Toolset version of the libmpx library is required, otherwise the application might not link properly.
  • The two binutils linkers, gold and ld, have different ways of handling hidden symbols, which leads to incompatibilities in their behavior. Previously, the gold and ld linkers had inconsistent and incorrect behavior with regard to shared libraries and hidden symbols. There were two scenarios:
    • If a shared library referenced a symbol that existed elsewhere in both hidden and non-hidden versions, the gold linker produced a bogus warning message about the hidden version.
    • If a shared library referenced a symbol that existed elsewhere only as a hidden symbol, the gold linker created an executable, even though it could not work.
    The gold linker has been updated so that it no longer issues bogus warning messages about hidden symbols that also exist in a non-hidden version. The second scenario cannot be solved in the linker. It is up to the programmer to ensure that a non-hidden version of the symbol is available when the application is run.
    As a result, the two linkers' behavior is closer, but they still differ in case of a reference to a hidden symbol that cannot be found elsewhere in a non-hidden version. Unfortunately, there is not a single correct behavior for this situation, so the linkers are allowed to differ.
  • The valgrind-openmpi subpackage is no longer provided with Valgrind in Red Hat Developer Toolset. The devtoolset-<version>-valgrind-openmpi subpackages previously caused incompatibility issues with various Red Hat Enterprise Linux minor releases and problems with rebuilding. Users are recommended to use the latest Red Hat Enterprise Linux system version of the valgrind and valgrind-openmpi packages if they need to run Valgrind against their programs that are built against the openmpi-devel libraries.