> I've gone ahead and marked it as "Committed", as that appears to have happened
> back in August as 36389a060c. > If for whatever reason that was the Wrong Thing To Do, please let me know.
36389a060c commit enables ASLR for windows but does not include other changes required for Arm64.
I've attached a new version of the patch which excludes the already merged ASLR changes and add
small changes to handle latest changes in the build scripts.
On Thu, 3 Nov 2022 at 08:38, Ian Lawrence Barwick <barwick@gmail.com> wrote:
2022年9月1日(木) 13:42 Michael Paquier <michael@paquier.xyz>: > > On Wed, Aug 31, 2022 at 10:22:06PM -0400, Tom Lane wrote: > > Michael Paquier <michael@paquier.xyz> writes: > > > The input object could also be reworked so as we would not have any > > > ordering issues, say "<e>pre<f><g><n2>&deep</n2></g></f>post</e>". > > > Changing only the path, you could use "/e/n2" instead of "node()", so > > > as we'd always get the most internal member. > > > > Done that way. > > Cool, thanks. bowerbird looks happy after its first run. > > An argument in favor of backpatching is if one decides to build the > code with MSVC and patch the scripts to enable ASLR. However, nobody > has complained about that yet, so fine by me to leave this change only > on HEAD for now.
Apologies for the thread bump, but there is an entry for this thread in the current CF previously marked "Needs review":
