Blastwave

> What platform and config args did you use? The 64bit datatype might be something other than "long long" Thanks for the snap fast reply! This is Debian Linux "sid"...

OKay ... I am perhaps being a bit pedantic here ( nothing new ) and I can remove the "pedantic" options and also configure with --debug and "no-asm". This is...

As I slow through this I hit other problems : ``` . . . /usr/bin/gcc-9 -I. -Icrypto/include -Iinclude -fPIC -std=c90 -m32 -g -fno-builtin -march=i686 -mtune=i686 -Wl,-rpath=/opt/bw/lib,--enable-new-dtags -mpc80 -pthread -std=c90 -fno-builtin...

I needed a small patch inside a questionable bit of code which uses " if (1) " for some reason : ``` titan# titan# diff -u crypto/bio/b_addr.c.orig crypto/bio/b_addr.c --- crypto/bio/b_addr.c.orig...

``` I realize that this is the same bug due to some code slippage and here we are in 2023 with OpenSSL 3.1.3 : /usr/pkg/gcc10/bin/gcc -I. -Iinclude -Iapps/include -fPIC -pthread...

``` Going down the rabbit hole here I see the calls to int OSSL_PARAM_get_uint64(const OSSL_PARAM *p, uint64_t *val) actually get handed off to crypto/params.c which use thse two fellows :...

> no response, marking as inactive, to be closed at the end of 3.4 dev barring further input ``` I have been told repeatedly by various OpenSSL project folks that...