Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1w0LAP-001pBe-2j for pgsql-hackers@arkaria.postgresql.org; Wed, 11 Mar 2026 15:08:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1w0LAM-009aIr-0d for pgsql-hackers@arkaria.postgresql.org; Wed, 11 Mar 2026 15:08:06 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1w0LAL-009aIi-0h for pgsql-hackers@lists.postgresql.org; Wed, 11 Mar 2026 15:08:06 +0000 Received: from fout-b8-smtp.messagingengine.com ([202.12.124.151]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1w0LAJ-00000001co4-3OG6 for pgsql-hackers@lists.postgresql.org; Wed, 11 Mar 2026 15:08:04 +0000 Received: from phl-compute-03.internal (phl-compute-03.internal [10.202.2.43]) by mailfout.stl.internal (Postfix) with ESMTP id 7A1F51D001E2; Wed, 11 Mar 2026 11:08:02 -0400 (EDT) Received: from phl-frontend-04 ([10.202.2.163]) by phl-compute-03.internal (MEProxy); Wed, 11 Mar 2026 11:08:02 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarazel.de; h= cc:cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm1; t=1773241682; x=1773328082; bh=Wr9MNoYX/T OpSrnoCHY1/sLCpRXs7QCrzbnBRKUBzJ8=; b=AG7z8TdQy27KxQR5UgB3CY8ZWA 6iBHoylCD9LNXNxs7GCY5ETc+n4B2yU+v7Sko3joncN1POqRNdGnJLT7PfxocYFx Sh5VajvAwKaG6ZI5wmH4lK3p9wG8RrgW143IioTerYMwSZWanmVwH6qnRV0Buwmi wrU4LtZWO27OBv074HqKSV+Fta0qKGEo9N4uXIO8/jTQ5lCza+9QR+AbgF/x4skN U1uTW+nKLoIsh7ewZDBABPTkrB27ze/GHgw5JR7aLqg+m428d7hCXmu3zXZibmvK mXIUR0TNBvVL8QrAzBV38kwXAqtTvLbCxeqGQ+kFB5ebXacFl5fIh14eSoyw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t= 1773241682; x=1773328082; bh=Wr9MNoYX/TOpSrnoCHY1/sLCpRXs7QCrzbn BRKUBzJ8=; b=ZbyeYpPp7quLyEq04pjJ3cVn/70NQJIeNUA22QZWS/X9+qDJj1o uoa+FZhOep/F84hB72PahKWPeTaYZO7ui04OHOx9cv8QxtLtKXYzAtFUYIVi8joB 0G7/BLAesAzofHVmOAgh/qUyRR5ZJh/l+Pu1nijwpsLzcti3EvrCdHdzdWYtYZur fDgVTBbauPYedsdzJnsYOMLrxMflEOILZGaScgiUhRknrGfn9lYMrpPZ0lZ4cNtC +BhRXdmNH3KucV89uzUduEWj9SxmM8CzklV7UDj5Jrgc/kf1kDrfchSiFwWvPGMY zEP3ATd0xOvbnHv+iiaSsgl2g5jTVvcK61w== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefgedrtddtgddvkeegvddvucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfurfetoffkrfgpnffqhgenuceu rghilhhouhhtmecufedttdenucenucfjughrpeffhffvvefukfhfgggtuggjsehttdfstd dttddvnecuhfhrohhmpeetnhgurhgvshcuhfhrvghunhguuceorghnughrvghssegrnhgr rhgriigvlhdruggvqeenucggtffrrghtthgvrhhnpeeffffgledvffegtdevlefgtdeggf fhvdekgfegteeiveejkeetudelveejhfeugeenucevlhhushhtvghrufhiiigvpedtnecu rfgrrhgrmhepmhgrihhlfhhrohhmpegrnhgurhgvshesrghnrghrrgiivghlrdguvgdpnh gspghrtghpthhtohepvddpmhhouggvpehsmhhtphhouhhtpdhrtghpthhtohepsggvrhht rhgrnhguughrohhuvhhothdrphhgsehgmhgrihhlrdgtohhmpdhrtghpthhtohepphhgsh hqlhdqhhgrtghkvghrsheslhhishhtshdrphhoshhtghhrvghsqhhlrdhorhhg X-ME-Proxy: Feedback-ID: id4a34324:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 11 Mar 2026 11:08:01 -0400 (EDT) Date: Wed, 11 Mar 2026 11:08:01 -0400 From: Andres Freund To: Bertrand Drouvot Cc: pgsql-hackers@lists.postgresql.org Subject: Re: Make Intel's ICX compiler working Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, On 2026-03-11 14:44:11 +0000, Bertrand Drouvot wrote: > After having worked on [1], I tried to make use of the Intel's ICX compiler [2]. Why? We removed icc support because it was barely maintained and buggy. Why would we expect ICX to be different? What would we gain by supporting what is essentially an LLVM fork? > The reason is that ICX defaults to -fp-model=fast enabling unsafe floating-point > optimizations (see [4]). That alone makes me extremely hesitant to support it. If a compiler vendor thinks defaulting to generating wrong results is a sane idea, I don't trust them. > 2/ Issue on ICX's default runtime libraries > > For example, I was observing: > > postgres: postgres regression [local] CREATE SUBSCRIPTION: Relink > `/opt/intel/oneapi/compiler/2025.3/lib/libimf.so' with `/lib/x86_64-linux-gnu/libm.so.6' for IFUNC symbol `cosf' > > followed by a SIGSEGV. > > The reason is that ICX by default links against Intel runtime libraries such as > libimf.so, which provide IFUNC-based replacements for standard math functions (e.g. > cosf). When shared libraries built with ICX are loaded into a process that > also uses the system libm.so.6, the dynamic linker encounters conflicting > IFUNC resolvers and segfaults. > > The issue is solved by making use of -no-intel-lib ([7]). So their runtime is too buggy to be used as well. > I think that it makes sense to have ICX working (we took care of ICC in the past), > so PFA, a patch implementing those changes for both autoconf and meson. -many without some very very very good reasons. Greetings, Andres Freund