From: Linus Torvalds <torvalds@linux-foundation.org> To: Ard Biesheuvel <ardb@kernel.org> Cc: Russell King - ARM Linux admin <linux@armlinux.org.uk>, Florian Weimer <fweimer@redhat.com>, Arnd Bergmann <arnd@kernel.org>, "Cc: Android Kernel" <kernel-team@android.com>, "Theodore Ts'o" <tytso@mit.edu>, Peter Zijlstra <peterz@infradead.org>, Catalin Marinas <catalin.marinas@arm.com>, Masahiro Yamada <masahiroy@kernel.org>, Nick Desaulniers <ndesaulniers@google.com>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Will Deacon <will@kernel.org>, linux-arm-kernel <linux-arm-kernel@lists.infradead.org> Subject: Re: [PATCH] compiler.h: Raise minimum version of GCC to 5.1 for arm64 Date: Thu, 14 Jan 2021 10:43:07 -0800 [thread overview] Message-ID: <CAHk-=wjHTpG+gMx9vqrZgo8Uw0NqA2kNjS87o63Zv3=WG2K3zA@mail.gmail.com> (raw) In-Reply-To: <CAMj1kXFaDNRbDvr43VLEHFRHHS0sGGcF=iTfES4sxPg-rZ34NA@mail.gmail.com> On Thu, Jan 14, 2021 at 12:18 AM Ard Biesheuvel <ardb@kernel.org> wrote: > > So if the arguments are piling up, what is holding us back, other than > inertia? I think we can most certainly just try increasing the minimum version to 5.1 in the next merge window and see. > Note that banning 4.9 for arm64 and banning it in general should be > two different changes in any case, as the former will need to be > backported to -stable kernels as well. Yes. The arm64 issue is a clear and known bug, plus I suspect gcc-4.9 is ridiculously old in the arm64 ecosystem anyway. So the arm64 issue is a bug-fix, the follow-up of just upgrading gcc requirements in general would be a "keep up with the times, and allow those variable declarations in loops". Linus
WARNING: multiple messages have this Message-ID (diff)
From: Linus Torvalds <torvalds@linux-foundation.org> To: Ard Biesheuvel <ardb@kernel.org> Cc: Florian Weimer <fweimer@redhat.com>, Arnd Bergmann <arnd@kernel.org>, Theodore Ts'o <tytso@mit.edu>, Will Deacon <will@kernel.org>, Peter Zijlstra <peterz@infradead.org>, Catalin Marinas <catalin.marinas@arm.com>, Masahiro Yamada <masahiroy@kernel.org>, Nick Desaulniers <ndesaulniers@google.com>, Russell King - ARM Linux admin <linux@armlinux.org.uk>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, "Cc: Android Kernel" <kernel-team@android.com>, linux-arm-kernel <linux-arm-kernel@lists.infradead.org> Subject: Re: [PATCH] compiler.h: Raise minimum version of GCC to 5.1 for arm64 Date: Thu, 14 Jan 2021 10:43:07 -0800 [thread overview] Message-ID: <CAHk-=wjHTpG+gMx9vqrZgo8Uw0NqA2kNjS87o63Zv3=WG2K3zA@mail.gmail.com> (raw) In-Reply-To: <CAMj1kXFaDNRbDvr43VLEHFRHHS0sGGcF=iTfES4sxPg-rZ34NA@mail.gmail.com> On Thu, Jan 14, 2021 at 12:18 AM Ard Biesheuvel <ardb@kernel.org> wrote: > > So if the arguments are piling up, what is holding us back, other than > inertia? I think we can most certainly just try increasing the minimum version to 5.1 in the next merge window and see. > Note that banning 4.9 for arm64 and banning it in general should be > two different changes in any case, as the former will need to be > backported to -stable kernels as well. Yes. The arm64 issue is a clear and known bug, plus I suspect gcc-4.9 is ridiculously old in the arm64 ecosystem anyway. So the arm64 issue is a bug-fix, the follow-up of just upgrading gcc requirements in general would be a "keep up with the times, and allow those variable declarations in loops". Linus _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-01-14 18:44 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-12 22:48 [PATCH] compiler.h: Raise minimum version of GCC to 5.1 for arm64 Will Deacon 2021-01-12 22:48 ` Will Deacon 2021-01-12 22:57 ` Nick Desaulniers 2021-01-12 22:57 ` Nick Desaulniers 2021-01-12 23:06 ` Nathan Chancellor 2021-01-12 23:06 ` Nathan Chancellor 2021-01-13 2:14 ` Linus Torvalds 2021-01-13 2:14 ` Linus Torvalds 2021-01-13 2:35 ` Linus Torvalds 2021-01-13 2:35 ` Linus Torvalds 2021-01-13 15:02 ` Catalin Marinas 2021-01-13 15:02 ` Catalin Marinas 2021-01-13 16:07 ` Catalin Marinas 2021-01-13 16:07 ` Catalin Marinas 2021-01-13 17:57 ` Masahiro Yamada 2021-01-13 17:57 ` Masahiro Yamada 2021-01-13 18:33 ` Joe Perches 2021-01-13 18:33 ` Joe Perches 2021-01-13 19:15 ` Linus Torvalds 2021-01-13 19:15 ` Linus Torvalds 2021-01-13 21:44 ` Russell King - ARM Linux admin 2021-01-13 21:44 ` Russell King - ARM Linux admin 2021-01-13 22:08 ` Linus Torvalds 2021-01-13 22:08 ` Linus Torvalds 2021-01-14 8:18 ` Ard Biesheuvel 2021-01-14 8:18 ` Ard Biesheuvel 2021-01-14 18:43 ` Linus Torvalds [this message] 2021-01-14 18:43 ` Linus Torvalds 2021-01-14 19:51 ` Joe Perches 2021-01-14 19:51 ` Joe Perches 2021-01-14 21:18 ` Linus Torvalds 2021-01-14 21:18 ` Linus Torvalds 2021-01-15 0:30 ` Joe Perches 2021-01-15 0:30 ` Joe Perches 2021-01-15 23:24 ` Linus Torvalds 2021-01-15 23:24 ` Linus Torvalds 2021-02-27 7:16 ` Masahiro Yamada 2021-02-27 7:16 ` Masahiro Yamada
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='CAHk-=wjHTpG+gMx9vqrZgo8Uw0NqA2kNjS87o63Zv3=WG2K3zA@mail.gmail.com' \ --to=torvalds@linux-foundation.org \ --cc=ardb@kernel.org \ --cc=arnd@kernel.org \ --cc=catalin.marinas@arm.com \ --cc=fweimer@redhat.com \ --cc=kernel-team@android.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux@armlinux.org.uk \ --cc=masahiroy@kernel.org \ --cc=ndesaulniers@google.com \ --cc=peterz@infradead.org \ --cc=tytso@mit.edu \ --cc=will@kernel.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.