From: Nick Desaulniers <[email protected]>
To: Alexei Starovoitov <[email protected]>
Cc: Steven Rostedt <[email protected]>,
Segher Boessenkool <[email protected]>,
Peter Zijlstra <[email protected]>,
Florian Weimer <[email protected]>,
Sami Tolvanen <[email protected]>,
Mathieu Desnoyers <[email protected]>,
linux-kernel <[email protected]>,
Matt Mullins <[email protected]>, Ingo Molnar <[email protected]>,
Alexei Starovoitov <[email protected]>,
Daniel Borkmann <[email protected]>,
Dmitry Vyukov <[email protected]>,
Martin KaFai Lau <[email protected]>, Song Liu <[email protected]>,
Yonghong Song <[email protected]>, Andrii Nakryiko <[email protected]>,
John Fastabend <[email protected]>,
KP Singh <[email protected]>, netdev <[email protected]>,
bpf <[email protected]>, Kees Cook <[email protected]>,
Josh Poimboeuf <[email protected]>,
[email protected],
Bill Wendling <[email protected]>
Subject: Re: violating function pointer signature
Date: Thu, 19 Nov 2020 17:31:41 -0800 [thread overview]
Message-ID: <CAKwvOdmKjsJGbR7hHACk3qUgguy-HWvJQerwTnArE0AwhPgfcQ@mail.gmail.com> (raw)
In-Reply-To: <CAADnVQL8d5zKTE_TohUcGgKKp6K1Noo7M22t_hKYQjO_g0Mb0g@mail.gmail.com>
On Thu, Nov 19, 2020 at 9:05 AM Alexei Starovoitov
<[email protected]> wrote:
>
> On Thu, Nov 19, 2020 at 6:59 AM Steven Rostedt <[email protected]> wrote:
> > Linux obviously
> > supports multiple architectures (more than any other OS), but it is pretty
> > stuck to gcc as a compiler (with LLVM just starting to work too).
> >
> > We are fine with being stuck to a compiler if it gives us what we want.
>
> I beg to disagree.
> android, chrome and others changed their kernel builds to
> "make LLVM=1" some time ago.
> It's absolutely vital for the health of the kernel to be built with
> both gcc and llvm.
Our fleet of machines in the data centers is currently mid-ramp, at
around or slightly just over 50% of kernels built with Clang. Soon to
be 100%. So "a good chunk of Google services," too, FWIW.
OpenMandriva is on track for their 4.2 release to use LLVM for their kernels.
--
Thanks,
~Nick Desaulniers
next prev parent reply other threads:[~2020-11-20 1:32 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 22:51 [PATCH] tracepoint: Do not fail unregistering a probe due to memory allocation Steven Rostedt
2020-11-16 23:16 ` Steven Rostedt
2020-11-17 19:15 ` Mathieu Desnoyers
2020-11-17 19:21 ` Steven Rostedt
2020-11-17 19:47 ` Mathieu Desnoyers
2020-11-17 20:34 ` Steven Rostedt
2020-11-17 20:58 ` Steven Rostedt
2020-11-17 21:22 ` Mathieu Desnoyers
2020-11-17 22:16 ` Steven Rostedt
2020-11-17 23:08 ` Mathieu Desnoyers
2020-11-18 1:11 ` Steven Rostedt
2020-11-17 21:08 ` Mathieu Desnoyers
2020-11-18 13:21 ` violating function pointer signature Peter Zijlstra
2020-11-18 13:59 ` Florian Weimer
2020-11-18 14:12 ` Peter Zijlstra
2020-11-18 14:18 ` Florian Weimer
2020-11-18 14:34 ` [PATCH v3] tracepoint: Do not fail unregistering a probe due to memory allocation Steven Rostedt
2020-11-24 5:59 ` Matt Mullins
2020-11-18 14:22 ` violating function pointer signature Steven Rostedt
2020-11-18 19:46 ` Alexei Starovoitov
2020-11-18 20:02 ` Steven Rostedt
2020-11-18 14:02 ` Steven Rostedt
2020-11-18 16:01 ` Mathieu Desnoyers
2020-11-18 16:19 ` David Laight
2020-11-18 16:50 ` Nick Desaulniers
2020-11-18 17:17 ` Steven Rostedt
2020-11-18 18:12 ` Segher Boessenkool
2020-11-18 18:31 ` Florian Weimer
2020-11-18 18:55 ` Segher Boessenkool
2020-11-18 18:58 ` Steven Rostedt
2020-11-18 18:59 ` Steven Rostedt
2020-11-18 19:11 ` Segher Boessenkool
2020-11-18 19:33 ` Steven Rostedt
2020-11-18 19:48 ` Segher Boessenkool
2020-11-18 20:44 ` Steven Rostedt
2020-11-19 8:21 ` Peter Zijlstra
2020-11-19 8:36 ` Peter Zijlstra
2020-11-19 14:37 ` Segher Boessenkool
2020-11-19 14:59 ` Steven Rostedt
2020-11-19 16:35 ` Segher Boessenkool
2020-11-19 17:42 ` David Laight
2020-11-19 19:27 ` Segher Boessenkool
2020-11-19 17:04 ` Alexei Starovoitov
2020-11-19 17:30 ` Steven Rostedt
2020-11-20 1:31 ` Nick Desaulniers [this message]
2020-11-17 21:33 ` [PATCH] tracepoint: Do not fail unregistering a probe due to memory allocation Kees Cook
2020-11-17 22:19 ` Steven Rostedt
2020-11-17 23:12 ` Mathieu Desnoyers
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=CAKwvOdmKjsJGbR7hHACk3qUgguy-HWvJQerwTnArE0AwhPgfcQ@mail.gmail.com \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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;
as well as URLs for NNTP newsgroup(s).