Adapt Titan compiler version checking to new gcc/clang versioning scheme
Submitted by Elemer Lelik
Link to original bug (#564194)
Description
Titan demands major and minor levels of gcc/clang to be equal and does not consider the patch level. This practice was correct up to GCC4 being consistent with gcc versioning. https://gcc.gnu.org/develop.html
From GCC5 gcc version numbering changed and uses only three numbers:
<major_version>
.<patch_level>
.0
The third number does not refer to patch level as before but to the version being a released or development one: 0 – released 1 – dev branch
So for instance: 7.4.0 – released, 4th patch of the GCC7 7.4.1 – The dev branch during the development of the 4th patch of the GCC7, after release become 7.4.0
Clang also dropped minor versions from Clang5.
so in summary the version numberings are:
GCC: <major>
.<patch>
.0
Clang: <major>
.0.<patch>
Titan's compiler version checking should be adapted to this new versioning scheme.
Version: 6.6.1