[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200123171641.GC20126@willie-the-truck>
Date: Thu, 23 Jan 2020 17:16:41 +0000
From: Will Deacon <will@...nel.org>
To: David Laight <David.Laight@...LAB.COM>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>,
"kernel-team@...roid.com" <kernel-team@...roid.com>,
Michael Ellerman <mpe@...erman.id.au>,
Peter Zijlstra <peterz@...radead.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Segher Boessenkool <segher@...nel.crashing.org>,
Christian Borntraeger <borntraeger@...ibm.com>,
Luc Van Oostenryck <luc.vanoostenryck@...il.com>,
Arnd Bergmann <arnd@...db.de>,
Peter Oberparleiter <oberpar@...ux.ibm.com>,
Masahiro Yamada <masahiroy@...nel.org>,
Nick Desaulniers <ndesaulniers@...gle.com>
Subject: Re: [PATCH v2 00/10] Rework READ_ONCE() to improve codegen
On Thu, Jan 23, 2020 at 05:07:40PM +0000, David Laight wrote:
> From: Will Deacon
> > Sent: 23 January 2020 15:34
> ...
> > * Only warn once at build-time if GCC prior to 4.8 is detected...
> >
> > * ... and then raise the minimum GCC version to 4.8, with an error for
> > older versions of the compiler
>
> If the kernel compiled with gcc 4.7 is likely to be buggy, don't these
> need to be in the other order?
>
> Otherwise you need to keep the old versions for use with the old
> compilers.
I think it depends how much we care about those older compilers. My series
first moves it to "Good luck mate, you're on your own" and then follows up
with a "Let me take that off you it's sharp".
Will
Powered by blists - more mailing lists