Re: --with-llvm on 32-bit platforms?

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Dmitry Mityugov <d(dot)mityugov(at)postgrespro(dot)ru>, Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: --with-llvm on 32-bit platforms?
Date: 2025-09-15 23:09:02
Message-ID: CA+hUKGKmfUA3mDojQOffHbNPiQxm1p3ce_QYvJSEnVy61Wom9A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Sep 16, 2025 at 8:22 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Dmitry Mityugov <d(dot)mityugov(at)postgrespro(dot)ru> writes:
> > What's interesting is that when I add the following (quick and dirty)
> > assertion to DatumGetPointer on 32-bit Linux platforms,
>
> > DatumGetPointer(Datum X)
> > {
> > Assert((X & 0xFFFFFFFF00000000) == 0);
> > return (Pointer) (uintptr_t) X;
> > }
>
> > I get a failure in Postgres executable early on startup.
>
> Interesting, but again, how about a stack trace?

Hmm. We use TypeSizeT in generated IR for Datum, which is obviously
incorrect in this configuration.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2025-09-15 23:37:32 Re: PgStat_HashKey padding issue when passed by reference
Previous Message Andres Freund 2025-09-15 23:05:37 Re: Buffer locking is special (hints, checksums, AIO writes)