As another test, I used:
[CODE]2164055665608607740612407885850964992308600790456484211778583267500488594259697867055939683405523563952275457830655867366860891 = 1079990819 x 2434978091641012135177 x P96 [/CODE]

With the following command:
[CODE]$ echo "2164055665608607740612407885850964992308600790456484211778583267500488594259697867055939683405523563952275457830655867366860891" | ecm_gpu.exe -v -gpu -gpucurves 214 -one -savea test.txt 50000 0[/CODE]

And get:
[CODE]Computing 224 Step 1 took 624ms of CPU time / 9409ms of GPU time
Throughput: 23.807 curves by second (on average 42.00ms by Step 1)
********** Factor found in step 1: 1079990819
Found probable prime factor of 10 digits: 1079990819
Composite cofactor 2003772279853619515456647493825560930355094796835012920400190242265835960092266179770126067530508853290794000565162089 has 118 digits
********** Factor found in step 1: 2434978091641012135177
Found probable prime factor of 22 digits: 2434978091641012135177
Probable prime cofactor 822911831006746846988611407569612756481494741933492587627928501694906928664977226688442425641057 has 96 digits[/CODE]

So I'm feeling pretty good that it works! If anybody encounters any errors, please let me know!

To push towards an upper limit, I used 2^4000-1 (which is fully factored). And I'm pleased to report that it worked perfectly!

Using B1=50000, I found a mess of the small factors in both stage 1 and 2.

[QUOTE=wombatman;375673]So I'm feeling pretty good that it works! If anybody encounters any errors, please let me know![/QUOTE]

Hello wombatman, I am very interested in the gmp-ecm with CUDA Windows binary that you have provided. However, since I am using Windows XP x64, your binary does not work on my system. I have been informed that programs compiled with Visual Studio 2012 and 2013 will normally only be compatible with Windows 7/8. I hear that if you use a "different compiler" or maybe "different compiling options" you could create a Windows XP compatible binary. Would you be willing to try to create an XP specific binary? If so, do you need any additional information to do this? If not, then... I look forward to the day I have a Windows 7 computer! :smile:

I would certainly be happy to try! If you know what settings I need to use, please feel free to tell me. In the meantime, I'll look around and see if I can figure out something! :smile:

Edit: Quick google search found this: [url]http://stackoverflow.com/questions/13130713/how-to-compile-for-win-xp-with-visual-studio-2012[/url]. I'll try it out and if it works, I'll post a binary here.

Edit #2: Looks like it did ok. This was compiled with v110_xp as the target, which is supposed to be good for Windows XP. The zip file includes the test.gpuecm file and the xaa.txt file so you can test both of them for Stage 1 and Stage 2, respectively. The max value for this compilation should be 2^8186-1 (actually 2^8192-1, but 6 bits are reserved for space or something).

I assume the XP version is working alright?

[QUOTE=wombatman;376082]I assume the XP version is working alright?[/QUOTE]

Unfortunately, no. When I tried to run $./test.gpuecm ecm_gpu_winxp.exe the program starts to run, but then I get a windows pop-up error message. This is on the first test in that file in an msys shell. The strange thing is that when I run the first, and second, test manually in msys or in a command prompt it completes successfully. When I manually run the 3rd or 4th test, both in msys or cmd, the program starts but then I get a windows pop-up error message.

I notice in the -printconfig that your version is compiled with MPIR 2.7.0 and with OpenMP. I'm sure MPIR 2.7.0, while not finalized yet, should be good for VS builds. However, I'm wondering if OpenMP might be causing problems on my system. Can you create a version with OpenMP turned off?

If you only get the error running the script, it seems like it might be the script itself. What is the pop-up error? And are you using MinGW? I assume so since you mention MSYS, but I just wanted to be sure.

Attached is the WinXP version, compiled with MPIR 2.7.0 and CC 2.0 with OpenMP disabled.

[QUOTE=wombatman;376111]If you only get the error running the script, it seems like it might be the script itself. What is the pop-up error? And are you using MinGW? I assume so since you mention MSYS, but I just wanted to be sure.

Attached is the WinXP version, compiled with MPIR 2.7.0 and CC 2.0 with OpenMP disabled.[/QUOTE]

It's not just with the script. It happens when I run the program manually, too. For me, MinGW is just a compiler. It's not used to run this ecm program or the test script. The only way I can run the test script is in an MSYS shell. Running the script (in MSYS), I get a crash on the first test. However, when I run all of the tests manually in an MSYS shell: test1 and test2 work fine, test3 and test4 will each start, but then produce a pop-up error message and crash. I run into the same thing when running these commands manually in a command prompt (cmd). When I run test1 and test2 in a cmd prompt, they both work fine. When I run test3 and test4 in a cmd prompt, they both crash, the same way they do in MSYS.

Here is test 4 from the test script:
#test for when stage 2 on CPU is needed
#echo "2^349-1" | $ECM -sigma 3:13 587 1261

Here is the result when I run it from MSYS or a cmd prompt:

[CODE]
$ echo "2^349-1" | ecm_gpu_winxp -sigma 3:13 587 1261
GMP-ECM 7.0-dev [configured with MPIR 2.7.0, --enable-gpu] [ECM]
Input number is 2^349-1 (106 digits)
Using B1=587, B2=1261, polynomial x^1, sigma=3:13
Step 1 took 0ms
<crash>
[/CODE]

I've included a screenshot of the error, it's not very informative. Here are the error messages that show up in the windows event log:
[CODE]
A couple of these:
Faulting application ecm_gpu_winxp.exe, version 0.0.0.0, faulting module nvcuda.dll, version 6.14.13.3165, fault address 0x0000000000094446.

A bunch of these:
Faulting application ecm_gpu_winxp.exe, version 0.0.0.0, faulting module ecm_gpu_winxp.exe, version 0.0.0.0, fault address 0x000000000001de4a.
[/CODE]

At this point, I can only think of a couple of possibilities:
1) Something on my computer is preventing me from successfully running test3 and test4.
2) Something in the code base or in Visual Studio isn't creating a binary that will run successfully on WinXP.

Do these binaries work for you? If so, then I'm at a loss. If not, then it could either be that WinXP binaries won't run on Win7, or that you have run into the same problem I'm seeing. In any event, if you don't want to do any more testing, we can just call WinXP a non-supported OS and move on. I was hoping to have a cuda enabled gmp-ecm, but I guess I can probably live without it. :wink: Thanks again for trying to create these for me.

I just ran the test.gpuecm file on my computer (windows 7), and the winxp exe file I posted passes tests 1 through 3 without issue. It doesn't work on test 4 within the script, and I'm not sure why (hence why it was commented out). Test 4 does work, if memory serves, when run manually.

What graphics card and CUDA version are you using? This was compiled for Compute Capability 2.0 (I have a GTX 570) with CUDA 6.0.

What do you get when you click the "To see what data this error report contains, click here" link?

Chris

[QUOTE=wombatman;376114]I just ran the test.gpuecm file on my computer (windows 7), and the winxp exe file I posted passes tests 1 through 3 without issue. It doesn't work on test 4 within the script, and I'm not sure why (hence why it was commented out). Test 4 does work, if memory serves, when run manually.

What graphics card and CUDA version are you using? This was compiled for Compute Capability 2.0 (I have a GTX 570) with CUDA 6.0.[/QUOTE]

I have a PNY GeForce GTX 650 with 1GB of GDDR5. I am running nVidia driver 331.65 for my Windows XP x64 system. I downloaded the CUDA 6.0.37 installer for Windows XP, but did not install it. I extracted the necessary cudart64_60.dll from the installer and put it in the same directory as your executable. This is what I believe allows test1 and test2 to successfully complete. As a quick test, I renamed that file and test1 now complains that cudart64_60.dll is missing. One other thing to mention, I am able to run the CUDA version of msieve in this setup without problem.

[QUOTE=chris2be8;376147]What do you get when you click the "To see what data this error report contains, click here" link?

Chris[/QUOTE]

I get another pop-up window that gives one of the above error messages, like:
[CODE]Faulting application ecm_gpu_winxp.exe, version 0.0.0.0, faulting module ecm_gpu_winxp.exe, version 0.0.0.0, fault address 0x000000000001de4a.[/CODE]
Then it says, "To view technical information about the error report, 'click here'." When you click on that it brings up another window that lists all of the loaded dll's related to the program (apparently 22 of them), and a stack dump of the running thread and the whole program. That pop-up also says, "The following files will be included in this error report". It lists one file, which I am attaching below. Unfortunately, these error messages don't seem to point to a definitive problem. :no: