From: David Laight <David.Laight@ACULAB.COM>
To: 'Adrian Bunk' <bunk@kernel.org>, Josh Triplett <josh@joshtriplett.org>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
"alex.gaynor@gmail.com" <alex.gaynor@gmail.com>,
"geofft@ldpreload.com" <geofft@ldpreload.com>,
"jbaublitz@redhat.com" <jbaublitz@redhat.com>,
Masahiro Yamada <masahiroy@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
"Greg KH" <gregkh@linuxfoundation.org>,
Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
clang-built-linux <clang-built-linux@googlegroups.com>
Subject: RE: Linux kernel in-tree Rust support
Date: Tue, 14 Jul 2020 08:27:20 +0000 [thread overview]
Message-ID: <732be8f3c8dc483785670259cc94dc26@AcuMS.aculab.com> (raw)
In-Reply-To: <20200712204501.GC25970@localhost>
From: Adrian Bunk
> Sent: 12 July 2020 21:45
....
> Rust gets updated frequently.
> Sometimes this also changes the LLVM version used by Rust.
> Debian stable supports targets like ARMv5 and 32bit MIPS.
> Distribution kernel updates are often automatically installed
> on user hardware.
This reminds me of why I never want to use an online compiler
service - never mind how hard companies push them.
If I need to do a bug-fix build of something that was released
2 (or more) years ago I want to use exactly the same toolchain
(warts and all) that was used for the original build.
If the compiler has changed I need to do a full test - just
in case it compiles some 'dodgy' code differently.
With the same compiler I only need to test the fix.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2020-07-14 8:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 18:41 Nick Desaulniers
2020-07-09 20:52 ` Miguel Ojeda
2020-07-10 5:36 ` Josh Triplett
2020-07-10 6:28 ` Greg KH
2020-07-10 12:50 ` Christian Brauner
2020-07-10 16:10 ` Kees Cook
[not found] ` <CAFRnB2WNo45J8h3-ncopLKENvcO0rf7J3xsy_eRKwFSpDD-5sQ@mail.gmail.com>
2020-07-10 23:05 ` Kees Cook
2020-07-10 22:59 ` Josh Triplett
2020-07-10 23:54 ` Linus Torvalds
2020-07-11 21:03 ` Josh Triplett
2020-07-28 20:40 ` Pavel Machek
2020-07-29 6:34 ` Josh Triplett
2020-12-17 21:45 ` Pavel Machek
2020-12-18 3:31 ` Miguel Ojeda
2020-07-11 17:13 ` Geoffrey Thomas
2020-07-12 12:31 ` Adrian Bunk
2020-07-12 19:39 ` Josh Triplett
2020-07-12 20:33 ` Linus Torvalds
2020-07-12 20:45 ` Adrian Bunk
2020-07-14 8:27 ` David Laight [this message]
2020-07-16 13:06 ` Arnd Bergmann
2020-07-16 23:12 ` Josh Triplett
2020-07-19 18:19 ` Adrian Bunk
2020-07-20 14:46 ` David Laight
2020-08-23 21:02 ` Adrian Bunk
2020-08-23 21:54 ` Geoffrey Thomas
2020-07-13 18:11 ` Eric W. Biederman
2020-07-13 21:33 ` Josh Triplett
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=732be8f3c8dc483785670259cc94dc26@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=alex.gaynor@gmail.com \
--cc=bunk@kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=geofft@ldpreload.com \
--cc=gregkh@linuxfoundation.org \
--cc=jbaublitz@redhat.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ndesaulniers@google.com \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.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
Powered by JetHome