[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <732be8f3c8dc483785670259cc94dc26@AcuMS.aculab.com>
Date: Tue, 14 Jul 2020 08:27:20 +0000
From: David Laight <David.Laight@...LAB.COM>
To: 'Adrian Bunk' <bunk@...nel.org>,
Josh Triplett <josh@...htriplett.org>
CC: Nick Desaulniers <ndesaulniers@...gle.com>,
"alex.gaynor@...il.com" <alex.gaynor@...il.com>,
"geofft@...reload.com" <geofft@...reload.com>,
"jbaublitz@...hat.com" <jbaublitz@...hat.com>,
Masahiro Yamada <masahiroy@...nel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"Greg KH" <gregkh@...uxfoundation.org>,
Miguel Ojeda <miguel.ojeda.sandonis@...il.com>,
Steven Rostedt <rostedt@...dmis.org>,
LKML <linux-kernel@...r.kernel.org>,
clang-built-linux <clang-built-linux@...glegroups.com>
Subject: RE: Linux kernel in-tree Rust support
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)
Powered by blists - more mailing lists