Expected RAM is 135431276999271530496 MB
The Executable is running into OOM (out of memory) and silently fails?
Topic: Pollard's kangaroo ECDLP solver - page 56. (Read 60698 times)
Anybody else see this:
What is problem detail?
try test compare with binary windows .exe release and you compile version Did both have problem?
Anybody else see this:
if I remark this line , I can compile a EXE ~~
Code:
Int.cpp
void Int::Div(Int *a,Int *mod)
qhat = _udiv128 (nh , nm , _dh , &qrem);
1>..\SECPK1\Int.cpp(1097): error C3861: '_udiv128': identifier not found
void Int::Div(Int *a,Int *mod)
qhat = _udiv128 (nh , nm , _dh , &qrem);
1>..\SECPK1\Int.cpp(1097): error C3861: '_udiv128': identifier not found
Don't do that, if you comment that out you will break division and Kangaroo won't work properly.
Windows has a problem with 128-bits multiplication and division intrinsics, they have to be emulated as macros by Kangaroo because they don't natively exist in the compiler (at least not until 2019 apparently).
What are you suggesting? That I compiled something else?
Well I used Visual Studio 2019 (Professional) on Windows 10 with CUDA 10.2 and Windows 10 SDK using the Visual Studio 2019 compiler (v142)
And if you google for _udiv128 you will find https://docs.microsoft.com/en-us/cpp/intrinsics/udiv128?view=msvc-160
Well I used Visual Studio 2019 (Professional) on Windows 10 with CUDA 10.2 and Windows 10 SDK using the Visual Studio 2019 compiler (v142)
And if you google for _udiv128 you will find https://docs.microsoft.com/en-us/cpp/intrinsics/udiv128?view=msvc-160
Quote
The _udiv128 intrinsic is available starting in Visual Studio 2019 RTM.
https://github.com/ZenulAbidin/Kangaroo-256
I can compile this project in Visual Studio 2015 + Windows 7 + CUDA 8 , only 1 errors ...
if I remark this line , I can compile a EXE ~~
Code:
Int.cpp
void Int::Div(Int *a,Int *mod)
qhat = _udiv128 (nh , nm , _dh , &qrem);
1>..\SECPK1\Int.cpp(1097): error C3861: '_udiv128': identifier not found
void Int::Div(Int *a,Int *mod)
qhat = _udiv128 (nh , nm , _dh , &qrem);
1>..\SECPK1\Int.cpp(1097): error C3861: '_udiv128': identifier not found
There are various compile versions.
Cuda 10
CUDA 10.2
CUDA 8
and CUDA 10.2 has targets for x32, x64 and x64 for SM 30 (which is actually targetting SM61)
So I will compile once for x64 with CUDA 10.2
EDIT:
here
https://github.com/ZenulAbidin/Kangaroo-256/issues/6
Cuda 10
CUDA 10.2
CUDA 8
and CUDA 10.2 has targets for x32, x64 and x64 for SM 30 (which is actually targetting SM61)
So I will compile once for x64 with CUDA 10.2
EDIT:
here
https://github.com/ZenulAbidin/Kangaroo-256/issues/6
Thank you! I will test it on a V100 and let you know of any issues.
Which project do you actually need to be compiled? I could compile all variations, but would like to just compile the specific one you want...
I just need Release-x64, and whatever CUDA version that works for you.
Last time I checked, there was only one project inside the solution (though my memory might be failing me), which is the main Kangaroo program, though there might be a second project for kangaroo tests. I just need the project for main Kangaroo.
EDIT: Yeah I saw your issue, now it's ready https://github.com/ZenulAbidin/Kangaroo-256/releases/tag/v2.3
There are various compile versions.
Cuda 10
CUDA 10.2
CUDA 8
and CUDA 10.2 has targets for x32, x64 and x64 for SM 30 (which is actually targetting SM61)
So I will compile once for x64 with CUDA 10.2
EDIT:
here
https://github.com/ZenulAbidin/Kangaroo-256/issues/6
Cuda 10
CUDA 10.2
CUDA 8
and CUDA 10.2 has targets for x32, x64 and x64 for SM 30 (which is actually targetting SM61)
So I will compile once for x64 with CUDA 10.2
EDIT:
here
https://github.com/ZenulAbidin/Kangaroo-256/issues/6
Which project do you actually need to be compiled? I could compile all variations, but would like to just compile the specific one you want...
Yup, the latest code here if you could compile would be great.
https://github.com/ZenulAbidin/Kangaroo-256
Sad to see there's no compiled .exe for the Kangaroo-256 fork. Compiling from the source throws a ton of errors, same with Jean_Luc's original version. But at least there is a working .exe for that one. I hope the dev finds time to compile the -256 fork on a Win machine 
I could successfully build the fork. But would you trust me if I publish the file?
I don't need to trust you. I just need to make sure your .exe doesn't have any network access. And since I'd run it inside an offline VM no need to worry about malware either. Thanks.
Which project do you actually need to be compiled? I could compile all variations, but would like to just compile the specific one you want...
Sad to see there's no compiled .exe for the Kangaroo-256 fork. Compiling from the source throws a ton of errors, same with Jean_Luc's original version. But at least there is a working .exe for that one. I hope the dev finds time to compile the -256 fork on a Win machine
I could successfully build the fork. But would you trust me if I publish the file?
Upload the exe somewhere like on zippyshare and then PM me the link so I can make a Github release out of it.
Thank you very much for your help, I appreciate it
Sad to see there's no compiled .exe for the Kangaroo-256 fork. Compiling from the source throws a ton of errors, same with Jean_Luc's original version. But at least there is a working .exe for that one. I hope the dev finds time to compile the -256 fork on a Win machine
I could successfully build the fork. But would you trust me if I publish the file?
So what exactly does your fork do? Make it able to search in a 256 bit range? Anything else?
Yea that's it, just make it able to search in a 256 bit range. That's all he was working on.
So what exactly does your fork do? Make it able to search in a 256 bit range? Anything else?
What is the url of the fork?
Sad to see there's no compiled .exe for the Kangaroo-256 fork. Compiling from the source throws a ton of errors, same with Jean_Luc's original version. But at least there is a working .exe for that one. I hope the dev finds time to compile the -256 fork on a Win machine
Jump to: