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

From Niyas Sait
Subject Re: [PATCH] Add native windows on arm64 support
Date
Msg-id CAFPTBD8Mk0X3h0UhWDbN7dLf1-eFeqcE8Qe3SUKzH9b+Gj1kBg@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Add native windows on arm64 support  (Michael Paquier <michael@paquier.xyz>)
Responses Re: [PATCH] Add native windows on arm64 support
List pgsql-hackers
> Why does it not allow that?  Is that just a limitation of the
> compiler?  If yes, what is the error happening?  This question is not
> exactly answered yet as of this thread.  I may be missing a reference
> about that in the upstream docs, but I see nowhere an explanation
> about the reason and the why.  That's also one of the first questions
> from Thomas upthread.

The following error occurs:

LINK : fatal error LNK1246: '/DYNAMICBASE:NO' not compatible with 'ARM64' target machine; link without '/DYNAMICBASE:NO

This seems to be a deliberate restriction for Arm64 targets. However, no references were provided. To clarify, I have posted a question [1] on the community channel of Visual Studio.

Niyas






On Thu, 21 Apr 2022 at 05:07, Michael Paquier <michael@paquier.xyz> wrote:
On Wed, Apr 20, 2022 at 10:43:06AM +0100, Niyas Sait wrote:
>> This issue is still lying around, and you may have been lucky.  Would
>> there be any issues to remove this change to get a basic support in?
>> As mentioned upthread, there is a long history of Postgres with ASLR.
>
> MSVC linker doesn't allow non-random base addresses for Arm64 platforms.
> It is needed for basic support.

Why does it not allow that?  Is that just a limitation of the
compiler?  If yes, what is the error happening?  This question is not
exactly answered yet as of this thread.  I may be missing a reference
about that in the upstream docs, but I see nowhere an explanation
about the reason and the why.  That's also one of the first questions
from Thomas upthread.
--
Michael

pgsql-hackers by date:

Previous
From: Yura Sokolov
Date:
Subject: Re: BufferAlloc: don't take two simultaneous locks
Next
From: Amit Kapila
Date:
Subject: Re: Data is copied twice when specifying both child and parent table in publication