Re: --with-llvm on 32-bit platforms? - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: --with-llvm on 32-bit platforms?
Date
Msg-id ed4b22aa-0e00-4ea5-ac40-3e474b9e218c@eisentraut.org
Whole thread Raw
In response to Re: --with-llvm on 32-bit platforms?  (Dmitry Mityugov <d.mityugov@postgrespro.ru>)
List pgsql-hackers
On 05.09.25 13:32, Dmitry Mityugov wrote:
> Dmitry Mityugov писал(а) 2025-09-05 11:11:
>> Dmitry Mityugov писал(а) 2025-09-05 00:32:
>>> It seems that when I add --with-llvm flag to ./configure on any 32- 
>>> bit platform that I have (Debian 12, Debian 13, Arch Linux), many 
>>> tests invoked by `make check` fail, or, sometimes, hang forever. Is 
>>> this a known problem? It's not critical to me, just wanted to know if 
>>> I should abandon --with-llvm forever on such platforms. On 64-bit 
>>> Linux platforms, both x86 and ARM, --with-llvm works fine.
>>>
>>> To reproduce, it's enough to:
>>>
>>> make distclean
>>> ./configure --with-llvm
>>> make -j23 -ks
>>> make check
>>>
>>> The last step is never successful to me, and, by the way, this can 
>>> also be reproduced with clang:
>>>
>>> make distclean
>>> ./configure CC=clang CXX=clang++ --with-llvm CFLAGS=-msse2
>>> make -j23 -ks
>>> make check
>>>
>>> Thanks in advance for your attention to this problem, or telling me 
>>> this is not a problem at all
>>
>> One of the reasons I ask this question is that according to 
>> f5d07085822a1 parameter --with-llvm is now mandatory in some cases, 
>> but it seems it can't be used.
> 
> By the way, when I rebuild REL_17_STABLE using the steps above (on 
> Debian 13 32-bit is this matters) tests in `make check` pass, so it 
> seems that something is broken in master.

It seems plausible that this is related to commit 2a600a93c7b "Make type 
Datum be 8 bytes wide everywhere.".  I don't have any more insights than 
that.




pgsql-hackers by date:

Previous
From: Чумак Антон
Date:
Subject: [PATCH] Introduce unified support for composite GUC options
Next
From: Alexander Korotkov
Date:
Subject: Re: Resetting recovery target parameters in pg_createsubscriber