Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1no1og-0000Ek-0D for pgsql-hackers@arkaria.postgresql.org; Mon, 09 May 2022 11:44:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1no1oe-0000sO-32 for pgsql-hackers@arkaria.postgresql.org; Mon, 09 May 2022 11:44:40 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1no1od-0000sF-PM for pgsql-hackers@lists.postgresql.org; Mon, 09 May 2022 11:44:39 +0000 Received: from mail-qk1-x733.google.com ([2607:f8b0:4864:20::733]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1no1oY-00087X-Ml for pgsql-hackers@lists.postgresql.org; Mon, 09 May 2022 11:44:38 +0000 Received: by mail-qk1-x733.google.com with SMTP id z126so10498948qkb.2 for ; Mon, 09 May 2022 04:44:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=KyVxkQda4jr947kEW4CBlH9D8K8x7MjnscWbYyQSFM4=; b=vhBSJsoF+g/S720G/52AM82mdNwzgmqItoUoK5rxTQVCB4BOr0zFcgeGs1IpLA32Dv OMO6UyBUGJlheOnUP4QFAdmaqRQRi9xPX24xmAnVbXSRKlXW1yfOG+10MmKKkFR2U2o8 r0VCdK725ixxfjjt3WTuFfM2Ay1oGg5ZcgXmHnkrRuwajnrHtHjC483tEIjRyB6dgLX5 gwpoeBFh2YIWlQyvnjE9XWQW6OV8rVzhni+OcLG7QF5YKKDY+/UXAQuvu9MvwNJUJXuT lAY2d0sgvhSk5ahjYMm+9Sn3EAWNCCRvG+rj0QQcDjR8w221nuzhbsDAMXgCRbPGYCNQ 5ODw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=KyVxkQda4jr947kEW4CBlH9D8K8x7MjnscWbYyQSFM4=; b=ZAIG+Go73voKRub1mrQwYtv7r/CXVc2VUIKr5QUXUU2wqRJOP5KF5IMojUr6o+eQxz 6VYB1Kf7YTwJu3dZe77WEWEJtrCQMT19hq0WIkqA2lPaHuGAxZt6FXH/Lb3G9RQFUraP 3QMAbP1lQ/cspwRhNBxOrSQhijm1QKS7ZhRdpOuk7aCqxD4WKAwdY9YrycCHc0hosXFY phOXwgPMb7A1acULMzeKdznmrcIdz4xvKnpkuesqF7QHBN9sTBBg4iz8pHPnSX0j4Hpz 7y4XNoAoLHXWogjlwXM/kmzs+qdVDs4C0WxV5/LbPpOkfooJn5vnKUxF4hchIvAB6YkV 32Xg== X-Gm-Message-State: AOAM530VxHTIUouhW61bcPCsdb+nc5Rg1JBUicnLYZ4IhCDnOOujU5QD WguuoIGZ5k7I+DV4yXYHqDyDzbzXx3g2bo8FYlDsFg== X-Google-Smtp-Source: ABdhPJw9W9UxVfVB6Ma/DA9YR1fMhZ7Je8fBvbFAbhFcK4xW2RfpoJy+knN1vEDXUi7DUB1eJgiIlJXy7E3OFfIYoQc= X-Received: by 2002:a05:620a:4107:b0:6a0:97f7:8d64 with SMTP id j7-20020a05620a410700b006a097f78d64mr2662427qko.675.1652096673643; Mon, 09 May 2022 04:44:33 -0700 (PDT) MIME-Version: 1.0 References: <3278490.1649338843@sss.pgh.pa.us> <20220407172258.uj5lgd6k25sngeno@alap3.anarazel.de> <3385302.1649353369@sss.pgh.pa.us> <20220407175359.h7gzgmmnbicq75d6@alap3.anarazel.de> In-Reply-To: From: Niyas Sait Date: Mon, 9 May 2022 12:44:22 +0100 Message-ID: Subject: Re: [PATCH] Add native windows on arm64 support To: Michael Paquier Cc: Andres Freund , Tom Lane , Thomas Munro , Julien Rouhaud , PostgreSQL Hackers Content-Type: multipart/alternative; boundary="0000000000005e140b05de92bb9c" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000005e140b05de92bb9c Content-Type: text/plain; charset="UTF-8" > Thanks for doing that! Your post is just a couple of days old, let's > see if we get a reply on that. Microsoft updated documentation [1] and clarified that ASLR cannot be disabled for Arm64 targets. Because ASLR can't be disabled on ARM, ARM64, or ARM64EC architectures, > /DYNAMICBASE:NO isn't supported for these targets. Thanks Niyas [1] https://docs.microsoft.com/en-us/cpp/build/reference/dynamicbase?view=msvc-170 On Mon, 25 Apr 2022 at 02:17, Michael Paquier wrote: > On Thu, Apr 21, 2022 at 10:21:04AM +0100, Niyas Sait wrote: > > The following error occurs: > > > > LINK : fatal error LNK1246: '/DYNAMICBASE:NO' not compatible with 'ARM64' > > target machine; link without '/DYNAMICBASE:NO > > Okay, that's interesting. In light of things like 7f3e17b, that may > be annoying. Perhaps newer Windows versions are able to handle that > better. I am wondering if it would be worth re-evaluating this > change, and attempt to re-enable that in environments other than > arm64. This could become interesting if we consider that there have > been talks to cut the support for a bunch of Windows versions to focus > on the newer ones only. > > > 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. > > Thanks for doing that! Your post is just a couple of days old, let's > see if we get a reply on that. > -- > Michael > --0000000000005e140b05de92bb9c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
> Thanks for doing that!=C2=A0 Your post is just a coup= le of days old, let's
> see if we get a reply on that.
Microsoft updated documentation [1] and clarified that ASLR ca= nnot be disabled for Arm64 targets.

Because ASLR can't be disabled on A= RM, ARM64, or ARM64EC architectures,=C2=A0/DYNAMICBASE:NO=C2=A0isn't s= upported for these targets.

Thanks
Niyas


On Mon, 25 Apr 2022 at 02:17, Michael Paquier <michael@paquier.xyz> wrote:
On Thu, Apr 21, 2022 at = 10:21:04AM +0100, Niyas Sait wrote:
> The following error occurs:
>
> LINK : fatal error LNK1246: '/DYNAMICBASE:NO' not compatible w= ith 'ARM64'
> target machine; link without '/DYNAMICBASE:NO

Okay, that's interesting.=C2=A0 In light of things like 7f3e17b, that m= ay
be annoying.=C2=A0 Perhaps newer Windows versions are able to handle that better.=C2=A0 I am wondering if it would be worth re-evaluating this
change, and attempt to re-enable that in environments other than
arm64.=C2=A0 This could become interesting if we consider that there have been talks to cut the support for a bunch of Windows versions to focus
on the newer ones only.

> 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.

Thanks for doing that!=C2=A0 Your post is just a couple of days old, let= 9;s
see if we get a reply on that.
--
Michael
--0000000000005e140b05de92bb9c--