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 213FC1B4244 for ; Sat, 20 Dec 2025 00:43:58 +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=1766191441; cv=none; b=dgPIf4RNsQxXx5HSxZMP+1voXGaG5Xo3hfKomHGg+41ML+34vaLxB1cOCLYfzG1N0Z+OF0l+XQrLn11z0IOAJZPdaAWYQ+Ysnx17zF+p1Z/VoO2sU2JxR1hoRP8GlC7obVpQfnZA8SLmfPwUevH+NqhQOhrBFnZnNIWHXjF+OdU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1766191441; c=relaxed/simple; bh=Aczg1W6HmWUCihDDG6UofcuXdh4NvvvZZFsLMIjuO8s=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=mLXj2f9+uVl4oAMiigxAv7Twy7jtY8ITUJ1UZIEB4o+KwFz0/7MFm1sXfj/0Mdj08i+OXNu7sfLqjwvuIR+Zbq98bScR/u8i9iLQgC5BzrEbXIvWMmJ6ghXHdHgmSAyoS5XGbojbwgBb4qLPG74jsk3MpLtGzYeRj+nb1dEGa/Q= 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=kbaFj/V+; 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="kbaFj/V+" Received: from [IPV6:2601:646:8081:9483:a140:2beb:fe7:432d] ([IPv6:2601:646:8081:9483:a140:2beb:fe7:432d]) (authenticated bits=0) by mail.zytor.com (8.18.1/8.17.1) with ESMTPSA id 5BK0hioj932376 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Fri, 19 Dec 2025 16:43:50 -0800 DKIM-Filter: OpenDKIM Filter v2.11.0 mail.zytor.com 5BK0hioj932376 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zytor.com; s=2025112201; t=1766191430; bh=WNEnwFn526x2LR2zQ3bF5pi8OkzTOwkkCM2SQZOu9Jw=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=kbaFj/V+fB6o2wnl/66c+Om8N+3unG04oK04u2vyyLPt2YfckAZY3yJA4t/v/Nvr3 jJH3IKZCXP8dJZZ4HUPcriqd/SLX0bWuRlSQ7AjFIFteoRLe0tXRgf+NEtPDQtBAH9 LiW8g99v/PVxbwde6C0gJKcnNmDY5dak2jSeOCXe3xLtoa8L7Lc4hsISZyfT1jC+NZ V1Gmh8WgYStSKRutEMiTOKIhXD0s5PdXYti9tPisVJg73ceHc4LDhPhRk4k4iV2Rjd DrXvfkGnACCXeO+UJbUXnnjt97yiVYMEVcff+V58CS3QCldinH3RiaH/K7rB0UUqaQ /UD++NP+/tX+g== Message-ID: Date: Fri, 19 Dec 2025 16:43:38 -0800 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Do we still care about compilers without __seg_fs and __seg_gs support?? To: Nathan Chancellor Cc: Uros Bizjak , Nick Desaulniers , Bill Wendling , Justin Stitt , "x86@kernel.org" , LKML , Andrew Morton References: <20251220002424.GA3998744@ax162> Content-Language: en-US, sv-SE From: "H. Peter Anvin" In-Reply-To: <20251220002424.GA3998744@ax162> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On 2025-12-19 16:24, Nathan Chancellor wrote: > > Trying to use __seg_fs or __seg_gs in certain cases crashes the X86 > backend. > > https://github.com/llvm/llvm-project/issues/93449 > > Is there anyone on AMD or Intel's LLVM teams that could look into > solving that? Nick pinged a couple of Intel's folks but it does not look > I don't know. As you know... things have been a bit crazy around these parts lately. -hpa