Re: [kernelci] Multiple compiler support in the backend

["Kevin Hilman" <khilman@baylibre.com>]

"Mark Brown" <broonie@kernel.org> writes:

> On Fri, Dec 14, 2018 at 03:01:04PM +0000, Guillaume Tucker wrote:
>
>> Potentially, we could have different flavours of the same
>> compiler version from different build environments.  Say, maybe
>> Linaro's GCC 8 will be different from Debian's etc...  Will the
>> build environment be shown in the email reports, or will there
>> still just be the compiler version as we do now?
>
> At least for GCC based toolchains the convention is for vendors to
> modify the version number of the compiler to indicate that they've added
> stuff - for example, on my desktop right now GCC reports that it is "gcc
> (Debian 8.2.0-6) 8.2.0", the Linaro toolchains do the same as do other
> binary toolchains I've looked at in the past.  That's probably enough I
> think?
>
> Sadly the clang-7 packages for Debian don't seem to have anything like
> that but my locally built copies of clang-8 have the git hash and repo
> URL for everything in the build.

The debian packages for recent clang builds I'm using are from
apt.llvm.org, and they seem to provide pretty detailed versioning:

   $ clang --version |head -1
   clang version 8.0.0-svn345496-1~exp1+0~20181029105533.852~1.gbpf10f36 (trunk)

Kevin