[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72==YbpCJPLOkCBGRkTYCOokLrEUNASn_JUpY2Ndw1sHfw@mail.gmail.com>
Date: Fri, 31 Mar 2023 15:39:35 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: David Gow <davidgow@...gle.com>
Cc: Richard Weinberger <richard@....at>,
Anton Ivanov <anton.ivanov@...bridgegreys.com>,
Johannes Berg <johannes@...solutions.net>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Nathan Chancellor <nathan@...nel.org>,
Miguel Ojeda <ojeda@...nel.org>,
Roberto Sassu <roberto.sassu@...weicloud.com>,
SeongJae Park <sj@...nel.org>, linux-um@...ts.infradead.org,
x86@...nel.org, llvm@...ts.linux.dev,
rust-for-linux@...r.kernel.org, kunit-dev@...glegroups.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] arch:um: Only disable SSE on clang to work around old GCC bugs
On Sat, Mar 18, 2023 at 5:16 AM David Gow <davidgow@...gle.com> wrote:
>
> Nevertheless, only disable SSE on clang setups, as that's a simple way
> of working around everyone's bugs.
Sounds good to me. If GCC >= 11 has fixed it, should we instead test
for GCC < 11, i.e. it could help catching future new regressions like
the linked GCC bug, if I understand correctly, right? Of course, that
could be done for the next cycle, since this one minimizes the
original change w.r.t. v6.2.
By the way, missing space on the title (`arch:um`).
Cheers,
Miguel
Powered by blists - more mailing lists