[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z89OmbYzIE2xyAD4@gmail.com>
Date: Mon, 10 Mar 2025 21:42:01 +0100
From: Ingo Molnar <mingo@...nel.org>
To: Uros Bizjak <ubizjak@...il.com>
Cc: Borislav Petkov <bp@...en8.de>, x86@...nel.org,
linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
Dave Hansen <dave.hansen@...ux.intel.com>,
"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH] x86/hweight: Fix and improve __arch_hweight{32,64}()
assembly
* Uros Bizjak <ubizjak@...il.com> wrote:
> On Mon, Mar 10, 2025 at 9:12 PM Borislav Petkov <bp@...en8.de> wrote:
> >
> > On Mon, Mar 10, 2025 at 09:08:04PM +0100, Uros Bizjak wrote:
> > > a) Use ASM_CALL_CONSTRAINT to prevent inline asm that includes call
> > > instruction from being scheduled before the frame pointer gets set
> > > up by the containing function, causing objtool to print a "call
> > > without frame pointer save/setup" warning.
> >
> > The other two are ok but this is new. How do you trigger this? I've never seen
> > it in my randconfig builds...
>
> It is not triggered now, but without this constraint, nothing prevents
> the compiler from scheduling the insn in front of frame creation.
Please add:
'Current versions of compilers don't seem to trigger this condition,
but without this constraint there's nothing to prevent the compiler
from scheduling the insn in front of frame creation.'
Thanks,
Ingo
Powered by blists - more mailing lists