[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=whH0EXPeWBCDT8Hf_6Dai7sd6KjccKXzixyZbWxREh3Cg@mail.gmail.com>
Date: Tue, 30 Jul 2024 13:13:18 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Guenter Roeck <linux@...ck-us.net>
Cc: Peter Zijlstra <peterz@...radead.org>, Jens Axboe <axboe@...nel.dk>,
Andy Lutomirski <luto@...nel.org>, Ingo Molnar <mingo@...hat.com>, Peter Anvin <hpa@...or.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, "the arch/x86 maintainers" <x86@...nel.org>
Subject: Re: Linux 6.11-rc1
On Tue, 30 Jul 2024 at 13:04, Guenter Roeck <linux@...ck-us.net> wrote:
>
> Maybe I should just switch to a more recent version of gcc and call it a day,
> in the hope that it is a compiler (or qemu) problem and doesn't just hide
> the problem.
Well, if it's a gcc-11 problem, I think we still really want to know
what is going on. We are *not* all that close to dropping support for
gcc-11 yet.
And honestly, while it's often very convenient to blame the compiler,
compiler bugs are still very rare.
It's *much* more common that bad code just happens to work with a good
compiler than that good code happens to break with a bad compiler.
Yes, we obviously do hit real compiler bugs, but still ... We'd need
to actually see what goes wrong in the code generation before blaming
a compiler bug.
Linus
Powered by blists - more mailing lists