From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.zytor.com (terminus.zytor.com [198.137.202.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id A1E57258CF7; Fri, 7 Mar 2025 23:29:15 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.137.202.136 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1741390159; cv=none; b=SaqHCc2GvBH1JBdXMD72AEKYc/gTZ2BIxDL+wx2qsQZlN4N7yOQcvIILqSQ/eCyRoLswEbHVOkkM7FRWyeZ5TtLS6qTF/H5UPHugacjxysb2hrwu/o84Vu4u5N8oaBlMyAL6EglLNsZBJ7r+Yjdy/t7uPTAKm0Wb9rXEDDfBsIA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1741390159; c=relaxed/simple; bh=Slall6SVSyYYujJBGzpuLGkq8QwY+nJRaF0FV5Ktvqo=; h=Date:From:To:CC:Subject:In-Reply-To:References:Message-ID: MIME-Version:Content-Type; b=YoeD8Q6SNeqd4VJpp+b19OuwgcZkOnzX5PCs59qH/IUsExYlzjjyybS9QdaxPz8cepO3B6MD7Cy97emjabVs5Yi3z0ZRSdrUuFwz1ydys72ldwgKxmY6pqubjFYLURwhNM9Aj6DtP77ciSR7g38WXJ/wTrzOb1dJzUkS32x6wtI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=zytor.com; spf=pass smtp.mailfrom=zytor.com; dkim=pass (2048-bit key) header.d=zytor.com header.i=@zytor.com header.b=CvZFoMLY; arc=none smtp.client-ip=198.137.202.136 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=zytor.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=zytor.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=zytor.com header.i=@zytor.com header.b="CvZFoMLY" Received: from [127.0.0.1] ([76.133.66.138]) (authenticated bits=0) by mail.zytor.com (8.18.1/8.17.1) with ESMTPSA id 527NT3V0486096 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Fri, 7 Mar 2025 15:29:04 -0800 DKIM-Filter: OpenDKIM Filter v2.11.0 mail.zytor.com 527NT3V0486096 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zytor.com; s=2025021701; t=1741390144; bh=Slall6SVSyYYujJBGzpuLGkq8QwY+nJRaF0FV5Ktvqo=; h=Date:From:To:CC:Subject:In-Reply-To:References:From; b=CvZFoMLY7RovTGG8TdpJlanme1cMcpP7psm6w0uPMIzwkkXGvBCStFeIL7AANlmE1 6L95Z+DdiP/LioKU6SYr08AJN53F1oFcx6Ts6tY9GApWkcyD+OuRb7CGWl6tvfzLKs Tcrl/DkXhmrYbTtbuz7vICDwAwVGMDF1CAayh4C7+Eax4cJKKPCwCd/ce2q5f1/Prt 7E3zgw5Jvw0yuA+McSqxeJvyoqM+WbCDXH//y8DCGt8sSuhuqFeRltq8RwgGcnSgeE AKC843gNmFgcJssTrt1WTljFYkMbLV/htdpAj1OxNQ1IUhfqF/2ahr3ctyK42n79F9 hbBCUlGqpvLiw== Date: Fri, 07 Mar 2025 15:29:00 -0800 From: "H. Peter Anvin" To: Josh Poimboeuf , Ingo Molnar CC: linux-kernel@vger.kernel.org, tip-bot2 for Josh Poimboeuf , linux-tip-commits@vger.kernel.org, "Peter Zijlstra (Intel)" , Linus Torvalds , Brian Gerst , x86@kernel.org Subject: =?US-ASCII?Q?Re=3A_=5Btip=3A_x86/asm=5D_x86/asm=3A_Make_ASM=5FCALL?= =?US-ASCII?Q?=5FCONSTRAINT_conditional_on_frame_pointers?= User-Agent: K-9 Mail for Android In-Reply-To: <20250307232157.comm4lycebr7zmre@jpoimboe> References: <174108458405.14745.4864877018394987266.tip-bot2@tip-bot2> <90B1074B-E7D4-4CE0-8A82-ADEB7BAED7AD@zytor.com> <20250307232157.comm4lycebr7zmre@jpoimboe> Message-ID: Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On March 7, 2025 3:21:57 PM PST, Josh Poimboeuf wro= te: >On Sat, Mar 08, 2025 at 12:05:29AM +0100, Ingo Molnar wrote: >>=20 >> * H=2E Peter Anvin wrote: >>=20 >> > > #endif /* __ASSEMBLY__ */ >> >=20 >> > So we are going to be using this version despite the gcc maintainers= =20 >> > telling us it is not supported? >>=20 >> No, neither patches are in the x86 tree at the moment=2E > >FWIW, the existing ASM_CALL_CONSTRAINT is also not supported, so this >patch wouldn't have changed anything in that respect=2E > >Regardless I plan to post a new patch set soon with a bunch of cleanups= =2E > >It will keep the existing ASM_CALL_CONSTRAINT in place for GCC, and will >use the new __builtin_frame_address(0) input constraint for Clang only=2E > >There will be a new asm_call() interface to hide the mess=2E > Alternatively, you can co-opt the gcc BR I already filed on this and argue= there that there are new reasons to support the alternate construct=2E