From: "Mark Brown" <broonie@kernel.org>
To: kernelci@groups.io, guillaume.tucker@gmail.com
Cc: Matt Hart <matthew.hart@linaro.org>
Subject: Re: [kernelci] Multiple compiler support in the backend
Date: Fri, 14 Dec 2018 18:19:10 +0000 [thread overview]
Message-ID: <20181214181910.GF6467@sirena.org.uk> (raw)
In-Reply-To: <CAH1_8nAj1h9ooiAOdmSWdP9TAGA_QnYx_-2UM2YrXV+4ACqh5w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 915 bytes --]
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-12-14 18:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 12:52 Multiple compiler support in the backend Matt Hart
2018-12-14 15:01 ` [kernelci] " Guillaume Tucker
2018-12-14 18:19 ` Mark Brown [this message]
2018-12-14 18:48 ` Kevin Hilman
2018-12-17 12:09 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181214181910.GF6467@sirena.org.uk \
--to=broonie@kernel.org \
--cc=guillaume.tucker@gmail.com \
--cc=kernelci@groups.io \
--cc=matthew.hart@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox