Re: [PATCH] Add native windows on arm64 support - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: [PATCH] Add native windows on arm64 support
Date
Msg-id CA+hUKG+bPsp45=86xoDeX2do4zOUaaD1nAhVmPhaO8k5OYs2LA@mail.gmail.com
Whole thread Raw
In response to [PATCH] Add native windows on arm64 support  (Niyas Sait <niyas.sait@linaro.org>)
Responses Re: [PATCH] Add native windows on arm64 support  (Niyas Sait <niyas.sait@linaro.org>)
List pgsql-hackers
On Wed, Feb 23, 2022 at 11:09 PM Niyas Sait <niyas.sait@linaro.org> wrote:
> I have created a patch that adds support for building Postgres for the windows/arm64 platform using the MSVC
toolchain.Following changes have been included
 
>
> 1. Extend MSVC scripts to handle ARM64 platform.
> 2. Add arm64 definition of spin_delay function.
> 3. Exclude arm_acle.h import with MSVC compiler.
>
> Compilation steps are consistent and similar to other windows platforms.
>
> The change has been tested on windows/x86_64 and windows/arm64 and all regression tests passes on both platforms.

+    # arm64 linker only supports dynamic base address
+    my $cfgrandbaseaddress = $self->{platform} eq 'ARM64' ? 'true' : 'false';
...
+      <RandomizedBaseAddress>$cfgrandbaseaddress</RandomizedBaseAddress>

Does that mean that you can't turn off ASLR on this arch?  Does it
cause random backend failures due to inability to map shared memory at
the expected address?  Our experience with EXEC_BACKEND on various
Unix systems tells us that you have to turn off ASLR if you want 100%
success rate on starting backends, but I guess it depends on the
details of how the randomisation is done.

Any interest in providing a build farm animal, so that we could know
that this works?



pgsql-hackers by date:

Previous
From: Pavel Borisov
Date:
Subject: Re: Probable CF bot degradation
Next
From: Thomas Munro
Date:
Subject: Re: Probable CF bot degradation