From: Linus Torvalds <torvalds@linux-foundation.org>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Will Deacon <will@kernel.org>, Arnd Bergmann <arnd@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
"Theodore Ts'o" <tytso@mit.edu>,
"Cc: Android Kernel" <kernel-team@android.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Florian Weimer <fweimer@redhat.com>
Subject: Re: [PATCH] compiler.h: Raise minimum version of GCC to 5.1 for arm64
Date: Wed, 13 Jan 2021 14:08:09 -0800 [thread overview]
Message-ID: <CAHk-=wjqGRXUp6KOdx-eHYEotGvY=a5tSY1mF-BkAcX2YAuBYw@mail.gmail.com> (raw)
In-Reply-To: <20210113214436.GL1551@shell.armlinux.org.uk>
On Wed, Jan 13, 2021 at 1:44 PM Russell King - ARM Linux admin
<linux@armlinux.org.uk> wrote:
>
> So, maybe the Sparc issue was just a similar but different bug in gcc
> 4.9.x.
Good catch. And I know this bug has happened independently on
different architectures several times (I remember this on x86-64 as
well), so I started looking around.
And in fact, 4.9 was buggy on x86-64 too:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61904
And yeah, _that_ gcc bug wasn't actually x86-64 specific, but
apparently a generic instruction scheduling bug.
So it's an independent bug, but I do have to admit that the arguments
against 4.9 are piling up (even if that particular fix apparently got
fixed in the gcc branches and apparently backported to distro
compilers too).
Linus
WARNING: multiple messages have this Message-ID (diff)
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: 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: Wed, 13 Jan 2021 14:08:09 -0800 [thread overview]
Message-ID: <CAHk-=wjqGRXUp6KOdx-eHYEotGvY=a5tSY1mF-BkAcX2YAuBYw@mail.gmail.com> (raw)
In-Reply-To: <20210113214436.GL1551@shell.armlinux.org.uk>
On Wed, Jan 13, 2021 at 1:44 PM Russell King - ARM Linux admin
<linux@armlinux.org.uk> wrote:
>
> So, maybe the Sparc issue was just a similar but different bug in gcc
> 4.9.x.
Good catch. And I know this bug has happened independently on
different architectures several times (I remember this on x86-64 as
well), so I started looking around.
And in fact, 4.9 was buggy on x86-64 too:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61904
And yeah, _that_ gcc bug wasn't actually x86-64 specific, but
apparently a generic instruction scheduling bug.
So it's an independent bug, but I do have to admit that the arguments
against 4.9 are piling up (even if that particular fix apparently got
fixed in the gcc branches and apparently backported to distro
compilers too).
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-13 22:13 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 [this message]
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
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-=wjqGRXUp6KOdx-eHYEotGvY=a5tSY1mF-BkAcX2YAuBYw@mail.gmail.com' \
--to=torvalds@linux-foundation.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: link
Be 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.