simon-git: putty (pre-0.78): Simon Tatham

Wed Oct 12 20:09:08 BST 2022

TL;DR:
  06157672 Windows installer: remove explicit InstallScope setting.
  2222cd10 AES-GCM NEON: cope with missing vaddq_p128.

Repository:     https://git.tartarus.org/simon/putty.git
On the web:     https://git.tartarus.org/?p=simon/putty.git
Branch updated: pre-0.78
Committer:      Simon Tatham <anakin at pobox.com>
Date:           2022-10-12 20:09:08

commit 0615767224a5a5234b1916d45eca29cec1fe4a59
web diff https://git.tartarus.org/?p=simon/putty.git;a=commitdiff;h=0615767224a5a5234b1916d45eca29cec1fe4a59;hp=9fcfd679b49a015e95f70b3f0380243e0db8b035
Author: Simon Tatham <anakin at pobox.com>
Date:   Wed Oct 12 19:42:09 2022 +0100

    Windows installer: remove explicit InstallScope setting.

    It turns out this isn't actually necessary after all to make the
    installer behave in the expected way in the default case (giving a UAC
    prompt and installing systemwide). And I'm told it has undesirable
    consequences in more complicated cases, which I'm not expert enough in
    MSI to fully understand.

 windows/installer.wxs | 9 +--------
 1 file changed, 1 insertion(+), 8 deletions(-)

commit 2222cd104dc5bd424fe025b98c133c91195cf9f3
web diff https://git.tartarus.org/?p=simon/putty.git;a=commitdiff;h=2222cd104dc5bd424fe025b98c133c91195cf9f3;hp=0615767224a5a5234b1916d45eca29cec1fe4a59
Author: Simon Tatham <anakin at pobox.com>
Date:   Wed Oct 12 12:54:36 2022 +0100

    AES-GCM NEON: cope with missing vaddq_p128.

    In some compilers (I'm told clang 10, in particular), the NEON
    intrinsic vaddq_p128 is missing, even though its input type poly128_t
    is provided.

    vaddq_p128 is just an XOR of two vector registers, so that's easy to
    work around by casting to a more mundane type and back. Added a
    configure-time test for that intrinsic, and a workaround to be used in
    its absence.

 cmake/cmake.h.in      | 1 +
 crypto/CMakeLists.txt | 8 ++++++++
 crypto/aesgcm-neon.c  | 8 ++++++++
 3 files changed, 17 insertions(+)