From: "Mathieu Acher" <mathieu.acher@irisa.fr>
To: Nick Desaulniers <ndesaulniers@google.com>, kernelci@groups.io
Subject: Re: kci_build proposal
Date: Tue, 23 Jun 2020 00:28:04 -0700 [thread overview]
Message-ID: <31688.1592897284383266895@groups.io> (raw)
In-Reply-To: <CAKwvOdnaoaZPLqcn6yiFEpEVx=HmpRe1ExhLZfzLhHs7e7Atww@mail.gmail.com>
Hi Nick,
Thanks for your interest.
We didn't target and gather data about Clang, but it was only a technical limitation at that time.
Right now, it seems possible to build kernel configurations with Clang (thanks to kernelci tool chain) and we are very interested to invest some resources/time here.
Indeed, we could differentiate GCC and Clang build and see what's going on.
We can also pinpoint combinations of options that lead to failures: it can be useful to indicate the root cause of the issues and investigate whether it's specific to Clang.
I'm available to have a chat
next prev parent reply other threads:[~2020-06-23 7:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 16:36 kci_build proposal Dan Rue
2020-04-21 15:46 ` Guillaume Tucker
2020-04-21 15:53 ` Mark Brown
2020-04-21 17:32 ` Dan Rue
2020-04-21 17:28 ` Dan Rue
2020-05-22 18:22 ` Kevin Hilman
2020-05-27 19:58 ` Dan Rue
2020-05-28 6:43 ` Guillaume Tucker
2020-05-28 17:28 ` Dan Rue
2020-05-28 21:03 ` Guillaume Tucker
2020-05-29 15:53 ` Dan Rue
2020-06-15 13:22 ` "Audience"/"Guest" can join for this meeting running on 23rd? koti koti
2020-06-16 16:16 ` Mark Brown
2020-06-17 1:49 ` koti koti
2020-06-17 10:31 ` Mark Brown
2020-06-17 10:55 ` koti koti
2020-05-28 23:31 ` kci_build proposal Kevin Hilman
2020-05-29 7:42 ` Mathieu Acher
2020-05-29 10:44 ` Mark Brown
2020-05-29 14:27 ` Guillaume Tucker
2020-06-16 16:33 ` Nick Desaulniers
2020-06-23 7:28 ` Mathieu Acher [this message]
2020-06-23 23:48 ` Nick Desaulniers
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=31688.1592897284383266895@groups.io \
--to=mathieu.acher@irisa.fr \
--cc=kernelci@groups.io \
--cc=ndesaulniers@google.com \
/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