[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=witEwVvJ6Wh4xdP-sUkLQSwcRTtg_NSuGMMgvYmcs3teQ@mail.gmail.com>
Date: Mon, 8 Apr 2024 11:32:20 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Ingo Molnar <mingo@...nel.org>, Thomas Gleixner <tglx@...utronix.de>, Peter Anvin <hpa@...or.com>,
"the arch/x86 maintainers" <x86@...nel.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: More annoying code generation by clang
On Mon, 8 Apr 2024 at 01:49, Peter Zijlstra <peterz@...radead.org> wrote:
>
> Should this not carry a comment about the "ir" constraint wanting to be
> "g" except for clang being daft?
Yeah. Except I think I'll do something like
/* Clang messes up "g" as an asm source */
#define ASM_SOURCE_G "ir"
in <linux/compiler-clang.h>, and
#ifndef ASM_SOURCE_G
#define ASM_SOURCE_G "g"
#endif
in linux/compiler.h.
> (I really wish clang would go fix this, it keeps coming up time and
> again).
It's been reported long ago, it seems to be hard to fix.
I suspect the issue is that the inline asm format is fairly closely
related to the gcc machine descriptions (look at the machine
descriptor files in gcc, and if you can ignore the horrid LISP-style
syntax you see how close they are).
And clang has a different model and needs to "translate" things, and
that one doesn't translate.
It's not like we don't have workarounds for gcc bugs in this area too
(eg "asm_goto_output()", née "asm_volatile_goto()").
There was another bug in my patch, though: the output mask should
always be "unsigned long", not tied to the input type.
Linus
Powered by blists - more mailing lists