JayDDee
JayDDee
My best guess is there's something in your custom environment causing the error. As I previously mentioned there seems to be confusion between the compiler (inlining the function code) and...
> But in the case of gcc, does not it make the two things at the same run, compile and link? I am not a GCC expert so this is...
>So all this code is c or a mix of C and C++? Github reports 0.5% c++. That's a good question. The only c++ code is magimath.cpp. It isn't used...
> If you're linking a mix of C and C++ then using `g++` to link is generally correct. That's not the problem here, the problem is the change to what...
Unoptimized is not supported, -O3 is recommended but -O2 also works but with a noticble loss in performance. I'll make the code changes anyway for consistency with other inline definitions....
Awesome! So linking with g++ instead of gcc is not about c++ but linking math. Thanks.
> The `-I` option is a preprocessor option, so use `CPPFLAGS` for that, not `CFLAGS`, and not `CPP_FLAGS`. Brain fart, I meant CXXFLAGS but that was wrong too because the...
Removing the magimath hack worked on Linux but on Windows it segfaulted in sha256 code that was unchanged from the previous version. Something weird there that requires a deep dive....
It's located in algo/sha/sha256-hash.h which uses some trickery to call the correct targets. The crash I observerd was when calling sha256_ctx_init from scanhash_yespower. The CPU did not have SHA so...
v24.1 is released with a fix to the title issue. Regarding the gcc vs g++ linker issue, I don't have any leads. Perhaps it was the way I did the...