[openssl/openssl] d7af3f: fix vs2019 warning

[Gerd Hoffmann]

  Branch: refs/heads/master
  Home:   https://github.com/openssl/openssl
  Commit: d7af3f7aa7c0d311c472e65b00928771192e6a06
      https://github.com/openssl/openssl/commit/d7af3f7aa7c0d311c472e65b00928771192e6a06
  Author: Gerd Hoffmann <kraxel at redhat.com>
  Date:   2024-07-18 (Thu, 18 Jul 2024)

  Changed paths:
    M ssl/statem/statem_clnt.c

  Log Message:
  -----------
  fix vs2019 warning

windows vs2019 throws warnings when compiling openssl for edk2:

ERROR - Compiler #2220 from [2024-07-15 13:43:34] [build-stdout] d:\a\edk2\edk2\CryptoPkg\Library\OpensslLib\openssl\ssl\statem\statem_clnt.c(1895) : the following warning is treated as an error
WARNING - Compiler #4701 from [2024-07-15 13:43:34] [build-stdout] d:\a\edk2\edk2\CryptoPkg\Library\OpensslLib\openssl\ssl\statem\statem_clnt.c(1895) : potentially uninitialized local variable 'peer_rpk' used
WARNING - Compiler #4703 from [2024-07-15 13:43:34] [build-stdout] d:\a\edk2\edk2\CryptoPkg\Library\OpensslLib\openssl\ssl\statem\statem_clnt.c(1895) : potentially uninitialized local pointer variable 'peer_rpk' used

Explicitly initialize the peer_rpk variable to make the compiler happy.

Yes, it's a false positive, but you have to check the tls_process_rpk()
body in another source file to see that, which apparently is beyond the
compiler's capabilities.

Signed-off-by: Gerd Hoffmann <kraxel at redhat.com>

Reviewed-by: Neil Horman <nhorman at openssl.org>
Reviewed-by: Tom Cosgrove <tom.cosgrove at arm.com>
Reviewed-by: Tomas Mraz <tomas at openssl.org>
(Merged from https://github.com/openssl/openssl/pull/24895)



To unsubscribe from these emails, change your notification settings at https://github.com/openssl/openssl/settings/notifications