> I'm sorry to be late. > I was too busy and had to prepare 64 bit gdb (& 64 bit perl). > > It seems to be 32 bit perl (perl-5.24.0) problem. > (Generating 64 bit code with 32 bit perl.)
For reference, I'm using 32-bit perl version 5.10.1, minimally supported version, by default, i.e. *all* the time. Well, not on Solaris, on Linux, but I do use it with 64-bit builds. As well with cross-compile builds for a handful qemu-based environments, 32- and 64-bit ones, and with mingw/wine. As for Solaris, I can say that 32-bit perl version 5.12.5 works for me. Bottom line is that perl's 32-bitness doesn't seem to be the problem, on the contrary, it's actually *known* to be capable of generating 64-bit assembly code, and failure to do so will be caught swiftly. > Tested with openssl-1.1.0 instead of pre-6, > and on pure Solaris 10, without any VM. > > > (1) with 32 bit perl > Did test/hmactest under gdb, break, > confirmed it was in OPENSSL_cleanse, > "leaq -0(%rsi),%rsi" (not "lea 0(%rdi),%rdi") > and making a short loop. > > (2) with 64 bit perl > make test passed both with gcc 5.4.0 & developerstudio12.5. In other words it's effectively confirmed that it's not really OpenSSL problem, but likely to be a problem with specific Solaris perl binary. I wonder if you could find opportunity to post broken crypto/x86_64cpuid.s generated by this broken perl, please? -- Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4641 Please log in as guest with password guest if prompted -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev