Re: disallow big-endian on aarch64

From: Tomas Vondra <tomas(at)vondra(dot)me>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Cc: andres(at)anarazel(dot)de
Subject: Re: disallow big-endian on aarch64
Date: 2025-10-02 20:29:39
Message-ID: c1f322e3-2e6c-441c-8bf4-e2b5650e65be@vondra.me
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 10/2/25 22:16, Nathan Bossart wrote:
> Some recent work involving SIMD instructions on AArch64 made me wonder
> whether we support $SUBJECT. For reference, AArch64 is bi-endian, but
> AFAICT all current AAarch64 buildfarm machines are on macOS, Linux, or
> FreeBSD, which appear to require little-endian [0] [1] [2]. I know there
> are efforts to support Windows on AAarch64, but that requires
> little-endian, too [3]. Given the apparent convergence on little-endian,
> IMHO we should require it for Postgres, too. The attached patch adds some
> configure-time checks for this.
>

I don't follow the reasoning. If there are no aarch64 platforms running
in big-endian mode (at least not supported ones), then how would you
even build Postgres in such environment?

Also, what's the benefit of disabling it? Is it about disabling
something we can't meaningfully test (even though we still support other
big-endian platforms, right?). Or does it affect the SIMD stuff somehow?

regards

--
Tomas Vondra

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2025-10-02 20:32:18 Re: Teaching planner to short-circuit empty UNION/EXCEPT/INTERSECT inputs
Previous Message Nathan Bossart 2025-10-02 20:16:30 disallow big-endian on aarch64