Forum > Alternate Hardware platforms
OSX Multibeam OpenCL question
Raistmer:
--- Quote from: Joe Fox on 10 Oct 2014, 06:45:23 pm ---Ah, I examined the svn diff, and looks like the code is now wrapped with an ifdef USE_OPENCL_INTEL. When I set that macro in the CFLAGS, then my binary works again. Thank you!
That leads me to a question. What should the USE_OPENCL_??? macros be set at for a wide distribution build, like a beta build? For my local machine, which has an Intel GPU, the USE_OPENCL_INTEL makes sense, but what about for the new Mac Pro desktop workstations? They have an nvidia GPU if I recall correctly. How would a widely distributed binary that was compiled with USE_OPENCL_INTEL work for the nvidia system?
Thanks for the assistance!
-Joe
--- End quote ---
Currently we use 3 separate binaries for different GPU types. There are some pecularities for each GPU vendor so I consider easier to maintain 3 separate optimized builds instead of universal under-optimized one.
Raistmer:
--- Quote from: Joe Fox on 10 Oct 2014, 07:16:27 pm ---Looks like there may be another problem. My binary runs successfully, but doesn't produce valid results. Attached is the results.sah and stderr.txt from my latest run. For what it is worth this ran in 14 minutes and 10 seconds.
--- End quote ---
Glancing on your first log it seems you missed correct set of defines.
I'll post what I use for Windows here, maybe Urs will correct it for OS X specific.
Joe Fox:
Regarding maintaining the different binaries, that makes sense. Regarding the incorrect defines, thanks. I'll go back to the OSX list, as well as compare to the windows build list that you send.
Thanks
-Joe
Urs Echternacht:
--- Quote from: Joe Fox on 10 Oct 2014, 07:16:27 pm ---Looks like there may be another problem. My binary runs successfully, but doesn't produce valid results. Attached is the results.sah and stderr.txt from my latest run. For what it is worth this ran in 14 minutes and 10 seconds.
--- End quote ---
The "reference_work_unit.sah" in the "test_workunits" directory seems to be an old v6 workunit without autocorr-signal detection. Instead, try to use "refquick.wu" or "reftiny.wu" from "DynWUs" directory for quick testing.
Additionally i've tried to adapt the readme (see attached) you have been referring your work to for Intel GPU builds. You may want to compare the "-D" commandline switches (you used the term "macro" before) , also called "preprocessor directives", from your build to what is in there. Especially "-DSETI7" is important for good results.
Joe Fox:
Thank you Urs, I will go through these and report back.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version