GCC front ends yield more flexibility for developers
C++ 17 achieves more support from GCC 6.1. GCC 6.1 even improves locations.
Posted: May 09,2016
New C++ standards are bound to turn the GNU Compiler Collection more effective for developers. Both in terms of diagnostics and parallelism, these standards are likely to show signs of improvement and compliance. Approved in 2014, the C++ 14 standard is to be leveraged following a release of the GCC 6.1. The C++ 14 standard acts as the default option for the current C++ front end. Earlier the C++ front end used the C++ 98 standard as the default option.
GCC 6.1 depicts an enhanced version of the C++ 17 support, which is now being used on an experimental basis and is likely to be launched by the end of 2016. However, there are developers that still work with old C++ versions. These developers will now have to follow the instructions laid down by the GNU. They will need to access the FTP servers for using the free software version of GCC 6.1.
A number of software languages like Fortran, Objective-C, Java, C++, Ada and C have libraries and front ends with GCC. Both Fortran and C++ programming involving multiple platforms will find quality Open MP 4.5 backing under the Version 6.1 features. Performing OpenMP offloading will now turn a lot easier with certain processors once the compiler gets configured in the right manner. For programming based on directives, the OpenACC 2.0a specification achieves some support improvement under the latest version.