Sebastian Falbesoner

Fixed https://github.com/bitcoin-core/secp256k1/pull/1579#discussion_r1810896825 and rebased on master for easier comparison of branches (since #1553, the output location of the .so file changed from ./build/src to ./build/lib; not being aware of that,...

Regarding the [open question](https://github.com/bitcoin-core/secp256k1/pull/1579#discussion_r1810882446) of whether or not to include the _CHECKMEM_UNDEFINE macro in secp256k1_memclear in non-verify binaries or not, I compared the valgrind-builds on the pr branch with the...

>> OTOH, "ctime-tests should run with the same binary as in the release" then doesn't hold anymore. > > I don't think so. If we wrap the new _CHECKMEM_UNDEFINE within...

Concept ACK

> My understanding is that this change is mostly a convenience change for native Windows developers, so that it becomes easier to run binaries after compilation (without installing?). Even as...

@real-or-random: Thanks for the quick review, force-pushed with all the suggestions taken.

Concept ACK Might be worth noting that this is currently only available on POSIX systems (i.e. not available on Windows, but on all other systems that we support AFAICT) in...