OpenCL GPU miner by girino for ypool.net - edit: bug on AMD corrected

Started by girino, January 20, 2014, 05:56:33 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

slacking

Quote from: plane501 on January 26, 2014, 05:55:51 AM
error when run build5

windows 7 64bit HD7950 and build 4 runs normally


I have Windows 8.1 64 bit, overclocked Radeon 7950, -a gpuv6 -m512 (1024 crashes)...getting in the 930 cpm range.

http://i.imgur.com/LrIeoBq.jpg

girino

Quote from: plane501 on January 26, 2014, 05:55:51 AM
error when run build5

windows 7 64bit HD7950 and build 4 runs normally




                                                  ^

"C:\Users\John\AppData\Local\Temp\OCL469B.tmp.cl", line 255: error: expression
          must have pointer-to-struct-or-union type
        step0to15(0); step0to15(1); step0to15(2); step0to15(3);
                                                  ^

Error limit reached.
100 errors detected in the compilation of "C:\Users\John\AppData\Local\Temp\OCL4
69B.tmp.cl".
Compilation terminated.

Frontend phase failed compilation.

---  End log  ---
Assertion failed!

Program: H:\jhProtominer-win64-mingw-build5\jhProtominer\jhProtominer.exe
File: OpenCLObjects.cpp, Line 310

Expression: !error

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

probably used some dialect that AMD does not recognize. (tested on NVidia only). I will test with AMD later today and correct the errors. Thanks for the report.

Bigboppa

Same error here...  :(
win7_x64, 2x R9280
Hope you can fix this!  :-*

krpetrov

Quote from: plane501 on January 26, 2014, 05:55:51 AM
error when run build5

windows 7 64bit HD7950 and build 4 runs normally




                                                  ^

"C:\Users\John\AppData\Local\Temp\OCL469B.tmp.cl", line 255: error: expression
          must have pointer-to-struct-or-union type
        step0to15(0); step0to15(1); step0to15(2); step0to15(3);
                                                  ^

Error limit reached.
100 errors detected in the compilation of "C:\Users\John\AppData\Local\Temp\OCL4
69B.tmp.cl".
Compilation terminated.

Frontend phase failed compilation.

---  End log  ---
Assertion failed!

Program: H:\jhProtominer-win64-mingw-build5\jhProtominer\jhProtominer.exe
File: OpenCLObjects.cpp, Line 310

Expression: !error

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

Got same error too.

renesoft


plane501

error when run build5

windows 7 64bit HD7950 and build 4 runs normally




                                                  ^

"C:\Users\John\AppData\Local\Temp\OCL469B.tmp.cl", line 255: error: expression
          must have pointer-to-struct-or-union type
        step0to15(0); step0to15(1); step0to15(2); step0to15(3);
                                                  ^

Error limit reached.
100 errors detected in the compilation of "C:\Users\John\AppData\Local\Temp\OCL4
69B.tmp.cl".
Compilation terminated.

Frontend phase failed compilation.

---  End log  ---
Assertion failed!

Program: H:\jhProtominer-win64-mingw-build5\jhProtominer\jhProtominer.exe
File: OpenCLObjects.cpp, Line 310

Expression: !error

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

girino

Helo all,

I just released new binaries (ending with build5) in the same old place (see first post). Those binaries use a new sha512 code, tuned and optimized by my during the last few days. It is at least 15% faster than the old code.

Short Version: faster! gpuv7 is default, gpuv9 is the low memory mode.

TLDR version: The new "-a" options "gpuv7", "gpuv8" and "gpuv9" all use the new code. "gpuv9" is the low memory version, same as "gpuv3", using the new sha512 code. "gpuv8" is the same as "gpuv4" with the new code, and "gpuv7" is based on "gpuv6", but uses a linear collision avoidance hashtable instead of the plain hashtable used before. It is bound to find slightly more hashes at the cost of being a little bit slower. since in all my tests it produces better CPM, i made "gpuv7" the default mode. The old modes are still kept for compatibility (maybe my optimizations are not compatible with all GPUs, then you can always fall back to the old modes).

Please download and enjoy.

Thanks,
girino.


Bigboppa

Quote from: Bigboppa on January 23, 2014, 12:02:46 PM
With old jhProtominer-win64-mingw-build2 i had the problem, that after running smooth for 1-2 hours, monitor goes black and computer freezes. No chance but to reset whole machine. (One of the mining-gpu is also for monitor). This happened 3 times. Hopefully jhProtominer-win64-mingw-build4 has fixed this, i will report later...
Problem seems to be fixed! No more crashes for >6h.
2070 cpm with 2x 9280x @1080/1500MHz, -m1028  :D

renesoft

Realy great work! ~1000 cpm on 7970 with gpuv6 and 1024 mb of memory ( with 2048 work slow ~300 cpm)
thanks!

Bigboppa

With old jhProtominer-win64-mingw-build2 i had the problem, that after running smooth for 1-2 hours, monitor goes black and computer freezes. No chance but to reset whole machine. (One of the mining-gpu is also for monitor). This happened 3 times. Hopefully jhProtominer-win64-mingw-build4 has fixed this, i will report later...

girino

Quote from: bey on January 23, 2014, 10:15:36 AM
Quote from: FredZ on January 23, 2014, 10:09:23 AM
tested : 2x R9 290x  with -m512 / -m1024 or -m2048
The result is the same :


I had same bug than you fredz, it is enough to Launch it two time, and it works correctly...

how strange. Does it happen also with the other algorithms? (command line options: "-a gpuv3" and "-a gpuv4") .



bey

Quote from: FredZ on January 23, 2014, 10:09:23 AM
tested : 2x R9 290x  with -m512 / -m1024 or -m2048
The result is the same :


I had same bug than you fredz, it is enough to Launch it two time, and it works correctly...


FredZ

tested : 2x R9 290x  with -m512 / -m1024 or -m2048
The result is the same :