I've Built a Couple OSX CUDA Apps...

Message boards : Number crunching : I've Built a Couple OSX CUDA Apps...
Message board moderation

To post messages, you must log in.

Previous · 1 . . . 24 · 25 · 26 · 27 · 28 · 29 · 30 . . . 58 · Next

AuthorMessage
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1788871 - Posted: 20 May 2016, 0:44:23 UTC - in response to Message 1788860.  

I'll check it with just the Two 950s later tonight. I plan on removing the cards and booting into Mountain Lion so I can build another version of Petri's zp. I'll run the Yosemite update at the same time and that will result in another webdriver. Seems they have WebDriver-346.02.03f07 posted already.
ID: 1788871 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1788899 - Posted: 20 May 2016, 5:03:15 UTC

This is what it shows with just the Two 950s in Yosemite;

Fri May 20 00:54:55 2016 | | Starting BOINC client version 7.6.32 for x86_64-apple-darwin
Fri May 20 00:54:55 2016 | | CUDA: NVIDIA GPU 0: Graphics Device (driver version 7.5.29, CUDA version 7.5, compute capability 5.2, 2048MB, 1874MB available, 2022 GFLOPS peak)
Fri May 20 00:54:55 2016 | | CUDA: NVIDIA GPU 1: Graphics Device (driver version 7.5.29, CUDA version 7.5, compute capability 5.2, 2048MB, 1825MB available, 2022 GFLOPS peak)
Fri May 20 00:54:55 2016 | | OpenCL: NVIDIA GPU 0: Graphics Device (driver version 10.5.2 346.02.03f06, device version OpenCL 1.2, 2048MB, 1874MB available, 2022 GFLOPS peak)
Fri May 20 00:54:55 2016 | | OpenCL: NVIDIA GPU 1: Graphics Device (driver version 10.5.2 346.02.03f06, device version OpenCL 1.2, 2048MB, 1825MB available, 2022 GFLOPS peak)
Fri May 20 00:54:55 2016 | | OpenCL CPU: Intel(R) Xeon(R) CPU E5472 @ 3.00GHz (OpenCL driver vendor: Apple, driver version 1.1, device version OpenCL 1.2)
Fri May 20 00:54:55 2016 | SETI@home | Found app_info.xml; using anonymous platform
Fri May 20 00:54:55 2016 | SETI@home Beta Test | Found app_info.xml; using anonymous platform
Fri May 20 00:54:56 2016 | | Processor: 8 GenuineIntel Intel(R) Xeon(R) CPU E5472 @ 3.00GHz [x86 Family 6 Model 23 Stepping 6]
Fri May 20 00:54:56 2016 | | OS: Mac OS X 10.10.5 (Darwin 14.5.0)

That's great, IF you only want to use Two cards. Now...why would you only want to use Two cards?
It would be nice If BOINC could handle 3 or maybe 4 cards without going Bonkers.
It does handle Three 750TI without any trouble...even Three ATI cards work. Try it with Two 950s & a 750TI though.
ID: 1788899 · Report as offensive
Profile petri33
Volunteer tester

Send message
Joined: 6 Jun 02
Posts: 1668
Credit: 623,086,772
RAC: 156
Finland
Message 1788929 - Posted: 20 May 2016, 7:16:44 UTC - in response to Message 1788899.  
Last modified: 20 May 2016, 7:18:50 UTC

This is what it shows with just the Two 950s in Yosemite;

Fri May 20 00:54:55 2016 | | Starting BOINC client version 7.6.32 for x86_64-apple-darwin
Fri May 20 00:54:55 2016 | | CUDA: NVIDIA GPU 0: Graphics Device (driver version 7.5.29, CUDA version 7.5, compute capability 5.2, 2048MB, 1874MB available, 2022 GFLOPS peak)
Fri May 20 00:54:55 2016 | | CUDA: NVIDIA GPU 1: Graphics Device (driver version 7.5.29, CUDA version 7.5, compute capability 5.2, 2048MB, 1825MB available, 2022 GFLOPS peak)
Fri May 20 00:54:55 2016 | | OpenCL: NVIDIA GPU 0: Graphics Device (driver version 10.5.2 346.02.03f06, device version OpenCL 1.2, 2048MB, 1874MB available, 2022 GFLOPS peak)
Fri May 20 00:54:55 2016 | | OpenCL: NVIDIA GPU 1: Graphics Device (driver version 10.5.2 346.02.03f06, device version OpenCL 1.2, 2048MB, 1825MB available, 2022 GFLOPS peak)
Fri May 20 00:54:55 2016 | | OpenCL CPU: Intel(R) Xeon(R) CPU E5472 @ 3.00GHz (OpenCL driver vendor: Apple, driver version 1.1, device version OpenCL 1.2)
Fri May 20 00:54:55 2016 | SETI@home | Found app_info.xml; using anonymous platform
Fri May 20 00:54:55 2016 | SETI@home Beta Test | Found app_info.xml; using anonymous platform
Fri May 20 00:54:56 2016 | | Processor: 8 GenuineIntel Intel(R) Xeon(R) CPU E5472 @ 3.00GHz [x86 Family 6 Model 23 Stepping 6]
Fri May 20 00:54:56 2016 | | OS: Mac OS X 10.10.5 (Darwin 14.5.0)

That's great, IF you only want to use Two cards. Now...why would you only want to use Two cards?
It would be nice If BOINC could handle 3 or maybe 4 cards without going Bonkers.
It does handle Three 750TI without any trouble...even Three ATI cards work. Try it with Two 950s & a 750TI though.


How about these environment variables: CUDA_​VISIBLE_​DEVICES and CUDA_​DEVICE_​ORDER ?

See http://docs.nvidia.com/cuda/cuda-c-programming-guide/index.html#env-vars

Id try to export CUDA_​VISIBLE_​DEVICES=0,1,2 with all permutations and try to launch BOINC after each change. The order of devices may have an effect.

CUDA_​VISIBLE_​DEVICES=1,0,2 would probably list gtx750ti first.

Petri
To overcome Heisenbergs:
"You can't always get what you want / but if you try sometimes you just might find / you get what you need." -- Rolling Stones
ID: 1788929 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1789082 - Posted: 20 May 2016, 21:56:47 UTC - in response to Message 1788929.  
Last modified: 20 May 2016, 22:10:45 UTC

Nothing wrong with the CUDA part, it's working the same way it always has. The CUDA device order in BOINC is the same as in CUDA-Z. I'd rather not change something that is working.
On the other hand the OpenCL section is still Broken after running the recent Yosemite update and using the New Webdriver;

Fri May 20 17:41:24 2016 | | Starting BOINC client version 7.6.32 for x86_64-apple-darwin
Fri May 20 17:41:25 2016 | | NVIDIA GPU 1: Graphics Device cannot be used for CUDA or OpenCL computation with CUDA driver 6.5 or later
Fri May 20 17:41:25 2016 | | NVIDIA GPU 2: Graphics Device cannot be used for CUDA or OpenCL computation with CUDA driver 6.5 or later
Fri May 20 17:41:25 2016 | | CUDA: NVIDIA GPU 0: Graphics Device (driver version 7.5.29, CUDA version 7.5, compute capability 5.2, 2048MB, 1862MB available, 2022 GFLOPS peak)
Fri May 20 17:41:25 2016 | | CUDA: NVIDIA GPU 1: GeForce GTX 750 Ti (driver version 7.5.29, CUDA version 7.5, compute capability 5.0, 2048MB, 1878MB available, 1421 GFLOPS peak)
Fri May 20 17:41:25 2016 | | CUDA: NVIDIA GPU 2: Graphics Device (driver version 7.5.29, CUDA version 7.5, compute capability 5.2, 2048MB, 1716MB available, 2022 GFLOPS peak)
Fri May 20 17:41:25 2016 | | OpenCL: NVIDIA GPU 1: GeForce GTX 750 Ti (driver version 10.5.2 346.02.03f07, device version OpenCL 1.2, 2048MB, 1878MB available, 1421 GFLOPS peak)
Fri May 20 17:41:25 2016 | | OpenCL: NVIDIA GPU 1: Graphics Device (driver version 10.5.2 346.02.03f07, device version OpenCL 1.2, 2048MB, 2048MB available, 758 GFLOPS peak)
Fri May 20 17:41:25 2016 | | OpenCL: NVIDIA GPU 2: Graphics Device (driver version 10.5.2 346.02.03f07, device version OpenCL 1.2, 2048MB, 2048MB available, 758 GFLOPS peak)
Fri May 20 17:41:25 2016 | | OpenCL CPU: Intel(R) Xeon(R) CPU E5472 @ 3.00GHz (OpenCL driver vendor: Apple, driver version 1.1, device version OpenCL 1.2)
Fri May 20 17:41:25 2016 | SETI@home | Found app_info.xml; using anonymous platform
Fri May 20 17:41:25 2016 | | App version needs OpenCL but GPU doesn't support it
Fri May 20 17:41:25 2016 | SETI@home Beta Test | Found app_info.xml; using anonymous platform
Fri May 20 17:41:25 2016 | | App version needs OpenCL but GPU doesn't support it
Fri May 20 17:41:25 2016 | | Processor: 8 GenuineIntel Intel(R) Xeon(R) CPU E5472 @ 3.00GHz [x86 Family 6 Model 23 Stepping 6]
Fri May 20 17:41:25 2016 | | OS: Mac OS X 10.10.5 (Darwin 14.5.0)

Seems adding the 750TI causes BOINC to mix it with a GTX 950 resulting in the 750TI being ignored and the Two GTX 950s being labeled as pre-Fermi cards. This results in BOINC claiming the cards already identified as having Compute Capability 5 & 5.2 as Not having OpenCL with a CUDA driver higher than 6.

No OpenCL for You!

In other news I've begun testing CUDA zq and as with zp it appears the counts are off by at least 1, http://setiathome.berkeley.edu/workunit.php?wuid=2163314906
But, it is quite a bit faster than zi on these horrid blc4 guppis.
Are the blc5s going to be even Slower than the blc4s???
ID: 1789082 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1789337 - Posted: 21 May 2016, 21:51:52 UTC

Things are a little different in Darwin 15.5, however, the bottom line is still the same;

Sat May 21 17:25:36 2016 | | Starting BOINC client version 7.6.22 for x86_64-apple-darwin
Sat May 21 17:25:37 2016 | | NVIDIA GPU 1: GeForce GTX 950 cannot be used for CUDA or OpenCL computation with CUDA driver 6.5 or later
Sat May 21 17:25:37 2016 | | NVIDIA GPU 2: GeForce GTX 950 cannot be used for CUDA or OpenCL computation with CUDA driver 6.5 or later
Sat May 21 17:25:37 2016 | | CUDA: NVIDIA GPU 0: GeForce GTX 950 (driver version 7.5.29, CUDA version 7.5, compute capability 5.2, 2048MB, 1867MB available, 2022 GFLOPS peak)
Sat May 21 17:25:37 2016 | | CUDA: NVIDIA GPU 1: GeForce GTX 950 (driver version 7.5.29, CUDA version 7.5, compute capability 5.2, 2048MB, 1910MB available, 2022 GFLOPS peak)
Sat May 21 17:25:37 2016 | | CUDA: NVIDIA GPU 2: GeForce GTX 750 Ti (driver version 7.5.29, CUDA version 7.5, compute capability 5.0, 2048MB, 1911MB available, 1421 GFLOPS peak)
Sat May 21 17:25:37 2016 | | OpenCL: NVIDIA GPU 1: GeForce GTX 950 (driver version 10.11.10 346.03.10f01, device version OpenCL 1.2, 2048MB, 2048MB available, 758 GFLOPS peak)
Sat May 21 17:25:37 2016 | | OpenCL: NVIDIA GPU 2: GeForce GTX 750 Ti (driver version 10.11.10 346.03.10f01, device version OpenCL 1.2, 2048MB, 1911MB available, 1421 GFLOPS peak)
Sat May 21 17:25:37 2016 | | OpenCL: NVIDIA GPU 2: GeForce GTX 950 (driver version 10.11.10 346.03.10f01, device version OpenCL 1.2, 2048MB, 2048MB available, 758 GFLOPS peak)
Sat May 21 17:25:37 2016 | | OpenCL CPU: Intel(R) Xeon(R) CPU E5472 @ 3.00GHz (OpenCL driver vendor: Apple, driver version 1.1, device version OpenCL 1.2)
Sat May 21 17:25:37 2016 | SETI@home | Found app_info.xml; using anonymous platform
Sat May 21 17:25:37 2016 | SETI@home Beta Test | Found app_info.xml; using anonymous platform
Sat May 21 17:25:37 2016 | | Version change (7.6.32 -> 7.6.22)
Sat May 21 17:25:37 2016 | | Processor: 8 GenuineIntel Intel(R) Xeon(R) CPU E5472 @ 3.00GHz [x86 Family 6 Model 23 Stepping 6]
Sat May 21 17:25:37 2016 | | OS: Mac OS X 10.11.5 (Darwin 15.5.0)

BOINC Still says there are Two GPUs with the same number, and the GTX 950s are pre-Fermi cards.
Why is BOINC confusing a GTX 950 with a 9500 GT?

The CUDA device order is different, but, it's the same in CUDA-Z as in BOINC.
CLinfo says;

TomsMacPro:MacCLinfo Tom$ ./clinfo
Found 1 platform(s).
platform[0x7fff0000]: profile: FULL_PROFILE
platform[0x7fff0000]: version: OpenCL 1.2 (Apr 26 2016 00:05:53)
platform[0x7fff0000]: name: Apple
platform[0x7fff0000]: vendor: Apple
platform[0x7fff0000]: extensions: cl_APPLE_SetMemObjectDestructor cl_APPLE_ContextLoggingFunctions cl_APPLE_clut cl_APPLE_query_kernel_names cl_APPLE_gl_sharing cl_khr_gl_event
platform[0x7fff0000]: Found 4 device(s).
	device[0xffffffff]: NAME: Intel(R) Xeon(R) CPU           E5472  @ 3.00GHz
	device[0xffffffff]: VENDOR: Intel
	device[0xffffffff]: PROFILE: FULL_PROFILE
	device[0xffffffff]: VERSION: OpenCL 1.2 
	device[0xffffffff]: EXTENSIONS: cl_APPLE_SetMemObjectDestructor cl_APPLE_ContextLoggingFunctions cl_APPLE_clut cl_APPLE_query_kernel_names cl_APPLE_gl_sharing cl_khr_gl_event cl_khr_fp64 cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_byte_addressable_store cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_3d_image_writes cl_khr_image2d_from_buffer cl_APPLE_fp64_basic_ops cl_APPLE_fixed_alpha_channel_orders cl_APPLE_biased_fixed_point_image_formats cl_APPLE_command_queue_priority
	device[0xffffffff]: DRIVER_VERSION: 1.1
	device[0xffffffff]: Type: CPU 
	device[0xffffffff]: EXECUTION_CAPABILITIES: Kernel Native 
	device[0xffffffff]: GLOBAL_MEM_CACHE_TYPE: Read-Write (2)
	device[0xffffffff]: CL_DEVICE_LOCAL_MEM_TYPE: Global (2)
	device[0xffffffff]: SINGLE_FP_CONFIG: 0xbf
	device[0xffffffff]: QUEUE_PROPERTIES: 0x2
	device[0xffffffff]: VENDOR_ID: 4294967295
	device[0xffffffff]: MAX_COMPUTE_UNITS: 8
	device[0xffffffff]: MAX_WORK_ITEM_DIMENSIONS: 3
	device[0xffffffff]: MAX_WORK_GROUP_SIZE: 1024
	device[0xffffffff]: PREFERRED_VECTOR_WIDTH_CHAR: 16
	device[0xffffffff]: PREFERRED_VECTOR_WIDTH_SHORT: 8
	device[0xffffffff]: PREFERRED_VECTOR_WIDTH_INT: 4
	device[0xffffffff]: PREFERRED_VECTOR_WIDTH_LONG: 2
	device[0xffffffff]: PREFERRED_VECTOR_WIDTH_FLOAT: 4
	device[0xffffffff]: PREFERRED_VECTOR_WIDTH_DOUBLE: 2
	device[0xffffffff]: MAX_CLOCK_FREQUENCY: 3000
	device[0xffffffff]: ADDRESS_BITS: 64
	device[0xffffffff]: MAX_MEM_ALLOC_SIZE: 1610612736
	device[0xffffffff]: IMAGE_SUPPORT: 1
	device[0xffffffff]: MAX_READ_IMAGE_ARGS: 128
	device[0xffffffff]: MAX_WRITE_IMAGE_ARGS: 8
	device[0xffffffff]: IMAGE2D_MAX_WIDTH: 8192
	device[0xffffffff]: IMAGE2D_MAX_HEIGHT: 8192
	device[0xffffffff]: IMAGE3D_MAX_WIDTH: 2048
	device[0xffffffff]: IMAGE3D_MAX_HEIGHT: 2048
	device[0xffffffff]: IMAGE3D_MAX_DEPTH: 2048
	device[0xffffffff]: MAX_SAMPLERS: 16
	device[0xffffffff]: MAX_PARAMETER_SIZE: 4096
	device[0xffffffff]: MEM_BASE_ADDR_ALIGN: 1024
	device[0xffffffff]: MIN_DATA_TYPE_ALIGN_SIZE: 128
	device[0xffffffff]: GLOBAL_MEM_CACHELINE_SIZE: 6291456
	device[0xffffffff]: GLOBAL_MEM_CACHE_SIZE: 64
	device[0xffffffff]: GLOBAL_MEM_SIZE: 6442450944
	device[0xffffffff]: MAX_CONSTANT_BUFFER_SIZE: 65536
	device[0xffffffff]: MAX_CONSTANT_ARGS: 8
	device[0xffffffff]: LOCAL_MEM_SIZE: 32768
	device[0xffffffff]: ERROR_CORRECTION_SUPPORT: 0
	device[0xffffffff]: PROFILING_TIMER_RESOLUTION: 1
	device[0xffffffff]: ENDIAN_LITTLE: 1
	device[0xffffffff]: AVAILABLE: 1
	device[0xffffffff]: COMPILER_AVAILABLE: 1


	device[0x1022700]: NAME: GeForce GTX 750 Ti
	device[0x1022700]: VENDOR: NVIDIA
	device[0x1022700]: PROFILE: FULL_PROFILE
	device[0x1022700]: VERSION: OpenCL 1.2 
	device[0x1022700]: EXTENSIONS: cl_APPLE_SetMemObjectDestructor cl_APPLE_ContextLoggingFunctions cl_APPLE_clut cl_APPLE_query_kernel_names cl_APPLE_gl_sharing cl_khr_gl_event cl_khr_byte_addressable_store cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_APPLE_fp64_basic_ops cl_khr_fp64 cl_khr_3d_image_writes cl_khr_depth_images cl_khr_gl_depth_images cl_khr_gl_msaa_sharing cl_khr_image2d_from_buffer cl_APPLE_ycbcr_422 cl_APPLE_rgb_422 
	device[0x1022700]: DRIVER_VERSION: 10.11.10 346.03.10f01
	device[0x1022700]: Type: GPU 
	device[0x1022700]: EXECUTION_CAPABILITIES: Kernel 
	device[0x1022700]: GLOBAL_MEM_CACHE_TYPE: None (0)
	device[0x1022700]: CL_DEVICE_LOCAL_MEM_TYPE: Local (1)
	device[0x1022700]: SINGLE_FP_CONFIG: 0x9f
	device[0x1022700]: QUEUE_PROPERTIES: 0x2
	device[0x1022700]: VENDOR_ID: 16918272
	device[0x1022700]: MAX_COMPUTE_UNITS: 5
	device[0x1022700]: MAX_WORK_ITEM_DIMENSIONS: 3
	device[0x1022700]: MAX_WORK_GROUP_SIZE: 1024
	device[0x1022700]: PREFERRED_VECTOR_WIDTH_CHAR: 1
	device[0x1022700]: PREFERRED_VECTOR_WIDTH_SHORT: 1
	device[0x1022700]: PREFERRED_VECTOR_WIDTH_INT: 1
	device[0x1022700]: PREFERRED_VECTOR_WIDTH_LONG: 1
	device[0x1022700]: PREFERRED_VECTOR_WIDTH_FLOAT: 1
	device[0x1022700]: PREFERRED_VECTOR_WIDTH_DOUBLE: 1
	device[0x1022700]: MAX_CLOCK_FREQUENCY: 1110
	device[0x1022700]: ADDRESS_BITS: 64
	device[0x1022700]: MAX_MEM_ALLOC_SIZE: 536870912
	device[0x1022700]: IMAGE_SUPPORT: 1
	device[0x1022700]: MAX_READ_IMAGE_ARGS: 256
	device[0x1022700]: MAX_WRITE_IMAGE_ARGS: 16
	device[0x1022700]: IMAGE2D_MAX_WIDTH: 16384
	device[0x1022700]: IMAGE2D_MAX_HEIGHT: 16384
	device[0x1022700]: IMAGE3D_MAX_WIDTH: 2048
	device[0x1022700]: IMAGE3D_MAX_HEIGHT: 2048
	device[0x1022700]: IMAGE3D_MAX_DEPTH: 2048
	device[0x1022700]: MAX_SAMPLERS: 32
	device[0x1022700]: MAX_PARAMETER_SIZE: 4352
	device[0x1022700]: MEM_BASE_ADDR_ALIGN: 1024
	device[0x1022700]: MIN_DATA_TYPE_ALIGN_SIZE: 128
	device[0x1022700]: GLOBAL_MEM_CACHELINE_SIZE: 0
	device[0x1022700]: GLOBAL_MEM_CACHE_SIZE: 0
	device[0x1022700]: GLOBAL_MEM_SIZE: 2147483648
	device[0x1022700]: MAX_CONSTANT_BUFFER_SIZE: 65536
	device[0x1022700]: MAX_CONSTANT_ARGS: 9
	device[0x1022700]: LOCAL_MEM_SIZE: 49152
	device[0x1022700]: ERROR_CORRECTION_SUPPORT: 0
	device[0x1022700]: PROFILING_TIMER_RESOLUTION: 1000
	device[0x1022700]: ENDIAN_LITTLE: 1
	device[0x1022700]: AVAILABLE: 1
	device[0x1022700]: COMPILER_AVAILABLE: 1


	device[0x2022700]: NAME: GeForce GTX 950
	device[0x2022700]: VENDOR: NVIDIA
	device[0x2022700]: PROFILE: FULL_PROFILE
	device[0x2022700]: VERSION: OpenCL 1.2 
	device[0x2022700]: EXTENSIONS: cl_APPLE_SetMemObjectDestructor cl_APPLE_ContextLoggingFunctions cl_APPLE_clut cl_APPLE_query_kernel_names cl_APPLE_gl_sharing cl_khr_gl_event cl_khr_byte_addressable_store cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_APPLE_fp64_basic_ops cl_khr_fp64 cl_khr_3d_image_writes cl_khr_depth_images cl_khr_gl_depth_images cl_khr_gl_msaa_sharing cl_khr_image2d_from_buffer cl_APPLE_ycbcr_422 cl_APPLE_rgb_422 
	device[0x2022700]: DRIVER_VERSION: 10.11.10 346.03.10f01
	device[0x2022700]: Type: GPU 
	device[0x2022700]: EXECUTION_CAPABILITIES: Kernel 
	device[0x2022700]: GLOBAL_MEM_CACHE_TYPE: None (0)
	device[0x2022700]: CL_DEVICE_LOCAL_MEM_TYPE: Local (1)
	device[0x2022700]: SINGLE_FP_CONFIG: 0x9f
	device[0x2022700]: QUEUE_PROPERTIES: 0x2
	device[0x2022700]: VENDOR_ID: 33695488
	device[0x2022700]: MAX_COMPUTE_UNITS: 6
	device[0x2022700]: MAX_WORK_ITEM_DIMENSIONS: 3
	device[0x2022700]: MAX_WORK_GROUP_SIZE: 1024
	device[0x2022700]: PREFERRED_VECTOR_WIDTH_CHAR: 1
	device[0x2022700]: PREFERRED_VECTOR_WIDTH_SHORT: 1
	device[0x2022700]: PREFERRED_VECTOR_WIDTH_INT: 1
	device[0x2022700]: PREFERRED_VECTOR_WIDTH_LONG: 1
	device[0x2022700]: PREFERRED_VECTOR_WIDTH_FLOAT: 1
	device[0x2022700]: PREFERRED_VECTOR_WIDTH_DOUBLE: 1
	device[0x2022700]: MAX_CLOCK_FREQUENCY: 1316
	device[0x2022700]: ADDRESS_BITS: 64
	device[0x2022700]: MAX_MEM_ALLOC_SIZE: 536870912
	device[0x2022700]: IMAGE_SUPPORT: 1
	device[0x2022700]: MAX_READ_IMAGE_ARGS: 256
	device[0x2022700]: MAX_WRITE_IMAGE_ARGS: 16
	device[0x2022700]: IMAGE2D_MAX_WIDTH: 16384
	device[0x2022700]: IMAGE2D_MAX_HEIGHT: 16384
	device[0x2022700]: IMAGE3D_MAX_WIDTH: 2048
	device[0x2022700]: IMAGE3D_MAX_HEIGHT: 2048
	device[0x2022700]: IMAGE3D_MAX_DEPTH: 2048
	device[0x2022700]: MAX_SAMPLERS: 32
	device[0x2022700]: MAX_PARAMETER_SIZE: 4352
	device[0x2022700]: MEM_BASE_ADDR_ALIGN: 1024
	device[0x2022700]: MIN_DATA_TYPE_ALIGN_SIZE: 128
	device[0x2022700]: GLOBAL_MEM_CACHELINE_SIZE: 0
	device[0x2022700]: GLOBAL_MEM_CACHE_SIZE: 0
	device[0x2022700]: GLOBAL_MEM_SIZE: 2147483648
	device[0x2022700]: MAX_CONSTANT_BUFFER_SIZE: 65536
	device[0x2022700]: MAX_CONSTANT_ARGS: 9
	device[0x2022700]: LOCAL_MEM_SIZE: 49152
	device[0x2022700]: ERROR_CORRECTION_SUPPORT: 0
	device[0x2022700]: PROFILING_TIMER_RESOLUTION: 1000
	device[0x2022700]: ENDIAN_LITTLE: 1
	device[0x2022700]: AVAILABLE: 1
	device[0x2022700]: COMPILER_AVAILABLE: 1


	device[0x3022700]: NAME: GeForce GTX 950
	device[0x3022700]: VENDOR: NVIDIA
	device[0x3022700]: PROFILE: FULL_PROFILE
	device[0x3022700]: VERSION: OpenCL 1.2 
	device[0x3022700]: EXTENSIONS: cl_APPLE_SetMemObjectDestructor cl_APPLE_ContextLoggingFunctions cl_APPLE_clut cl_APPLE_query_kernel_names cl_APPLE_gl_sharing cl_khr_gl_event cl_khr_byte_addressable_store cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_APPLE_fp64_basic_ops cl_khr_fp64 cl_khr_3d_image_writes cl_khr_depth_images cl_khr_gl_depth_images cl_khr_gl_msaa_sharing cl_khr_image2d_from_buffer cl_APPLE_ycbcr_422 cl_APPLE_rgb_422 
	device[0x3022700]: DRIVER_VERSION: 10.11.10 346.03.10f01
	device[0x3022700]: Type: GPU 
	device[0x3022700]: EXECUTION_CAPABILITIES: Kernel 
	device[0x3022700]: GLOBAL_MEM_CACHE_TYPE: None (0)
	device[0x3022700]: CL_DEVICE_LOCAL_MEM_TYPE: Local (1)
	device[0x3022700]: SINGLE_FP_CONFIG: 0x9f
	device[0x3022700]: QUEUE_PROPERTIES: 0x2
	device[0x3022700]: VENDOR_ID: 50472704
	device[0x3022700]: MAX_COMPUTE_UNITS: 6
	device[0x3022700]: MAX_WORK_ITEM_DIMENSIONS: 3
	device[0x3022700]: MAX_WORK_GROUP_SIZE: 1024
	device[0x3022700]: PREFERRED_VECTOR_WIDTH_CHAR: 1
	device[0x3022700]: PREFERRED_VECTOR_WIDTH_SHORT: 1
	device[0x3022700]: PREFERRED_VECTOR_WIDTH_INT: 1
	device[0x3022700]: PREFERRED_VECTOR_WIDTH_LONG: 1
	device[0x3022700]: PREFERRED_VECTOR_WIDTH_FLOAT: 1
	device[0x3022700]: PREFERRED_VECTOR_WIDTH_DOUBLE: 1
	device[0x3022700]: MAX_CLOCK_FREQUENCY: 1316
	device[0x3022700]: ADDRESS_BITS: 64
	device[0x3022700]: MAX_MEM_ALLOC_SIZE: 536870912
	device[0x3022700]: IMAGE_SUPPORT: 1
	device[0x3022700]: MAX_READ_IMAGE_ARGS: 256
	device[0x3022700]: MAX_WRITE_IMAGE_ARGS: 16
	device[0x3022700]: IMAGE2D_MAX_WIDTH: 16384
	device[0x3022700]: IMAGE2D_MAX_HEIGHT: 16384
	device[0x3022700]: IMAGE3D_MAX_WIDTH: 2048
	device[0x3022700]: IMAGE3D_MAX_HEIGHT: 2048
	device[0x3022700]: IMAGE3D_MAX_DEPTH: 2048
	device[0x3022700]: MAX_SAMPLERS: 32
	device[0x3022700]: MAX_PARAMETER_SIZE: 4352
	device[0x3022700]: MEM_BASE_ADDR_ALIGN: 1024
	device[0x3022700]: MIN_DATA_TYPE_ALIGN_SIZE: 128
	device[0x3022700]: GLOBAL_MEM_CACHELINE_SIZE: 0
	device[0x3022700]: GLOBAL_MEM_CACHE_SIZE: 0
	device[0x3022700]: GLOBAL_MEM_SIZE: 2147483648
	device[0x3022700]: MAX_CONSTANT_BUFFER_SIZE: 65536
	device[0x3022700]: MAX_CONSTANT_ARGS: 9
	device[0x3022700]: LOCAL_MEM_SIZE: 49152
	device[0x3022700]: ERROR_CORRECTION_SUPPORT: 0
	device[0x3022700]: PROFILING_TIMER_RESOLUTION: 1000
	device[0x3022700]: ENDIAN_LITTLE: 1
	device[0x3022700]: AVAILABLE: 1
	device[0x3022700]: COMPILER_AVAILABLE: 1
TomsMacPro:MacCLinfo Tom$

So, BOINC OpenCL detection is still Borked. CLinfo has the same device order as CUDA.
ID: 1789337 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1790988 - Posted: 27 May 2016, 18:08:04 UTC
Last modified: 27 May 2016, 18:32:04 UTC

I was able to compile a couple OpenCL Apps in El Capitan so I swapped out a 750TI for an older ATI card. This is what BOINC shows in Yosemite, it'a about the same in El Capitan except the 950s are actually named 950s;

Fri May 27 11:56:16 2016 | | Starting BOINC client version 7.4.36 for x86_64-apple-darwin
Fri May 27 11:56:16 2016 | | CUDA: NVIDIA GPU 0: Graphics Device (driver version 7.5.29, CUDA version 7.5, compute capability 5.2, 2048MB, 1862MB available, 2022 GFLOPS peak)
Fri May 27 11:56:16 2016 | | CUDA: NVIDIA GPU 1: Graphics Device (driver version 7.5.29, CUDA version 7.5, compute capability 5.2, 2048MB, 1808MB available, 2022 GFLOPS peak)
Fri May 27 11:56:16 2016 | | OpenCL: NVIDIA GPU 0: Graphics Device (driver version 10.5.2 346.02.03f07, device version OpenCL 1.2, 2048MB, 1862MB available, 2022 GFLOPS peak)
Fri May 27 11:56:16 2016 | | OpenCL: NVIDIA GPU 1: Graphics Device (driver version 10.5.2 346.02.03f07, device version OpenCL 1.2, 2048MB, 1808MB available, 2022 GFLOPS peak)
Fri May 27 11:56:16 2016 | | OpenCL: AMD/ATI GPU 0: ATI Radeon Barts PRO Prototype (driver version 1.2 (Apr 21 2016 21:29:34), device version OpenCL 1.2, 1024MB, 1024MB available, 868 GFLOPS peak)
Fri May 27 11:56:16 2016 | | OpenCL CPU: Intel(R) Xeon(R) CPU E5472 @ 3.00GHz (OpenCL driver vendor: Apple, driver version 1.1, device version OpenCL 1.2)
Fri May 27 11:56:16 2016 | | Processor: 8 GenuineIntel Intel(R) Xeon(R) CPU E5472 @ 3.00GHz [x86 Family 6 Model 23 Stepping 6]
Fri May 27 11:56:16 2016 | | OS: Mac OS X 10.10.5 (Darwin 14.5.0)

Much better than BOINC claiming the 950s are pre-Fermi cards and only running 2 cards instead of three with OpenCL. Strange you get that pre-Fermi warning yet Two cards will work in OpenCL. Unfortunately it appears the two cards that run are a 750TI & GTX 950 and they are Both seen as a 950 meaning the 750TI uses the Same kernel files as the 950 and crashes...not good.

After a little testing it seems the ATI App gives Good results in both Yosemite and El Capitan running a little faster in El Capitan. It appears to find Gaussians on my old card, I'm not sure how it will work with the newer cards in a Mac Pro.
The nVidia OpenCL App works well in Yosemite and gives about the same run-times as the 'Special' CUDA App with the VLARs. This is Good. The Bad news is it slows down in El Capitan and gives mostly BAD results, which is what most other people are experiencing. So, nVidia users in El Capitan would be better off using the CUDA 'Special' App in El Capitan as it gives fewer Inconclusive results with about the same run-times on the VLARs.

So far, Every CUDA Special App I've compiled in Mavericks and above gives a number of the 'Crash After Finish' Errors whereas the Apps compiled in Mountain Lion with Toolkit 6.5 Don't give this Error. The Apps compiled with Toolkit 6.5 are a little slower on the VLARs, but Don't give any Errors.
It would be nice to Fix whatever is causing this Crash After the Correct results have been printed. I have tried numerous versions of BOINC and boinc-masters, they All have this problem with Apps compiled in Mavericks and above.
ID: 1790988 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1791772 - Posted: 29 May 2016, 18:33:56 UTC
Last modified: 29 May 2016, 19:01:30 UTC

So....
I finally placed the 8800 GT faceplate on a GTX 950 so it will fit in slot 4.
The results are;
Sun May 29 14:00:52 2016 | | NVIDIA GPU 2: GeForce GTX 750 Ti cannot be used for CUDA or OpenCL computation with CUDA driver 6.5 or later
Sun May 29 14:00:52 2016 | | CUDA: NVIDIA GPU 0: GeForce GTX 950 (driver version 7.5.29, CUDA version 7.5, compute capability 5.2, 2048MB, 1802MB available, 2022 GFLOPS peak)
Sun May 29 14:00:52 2016 | | CUDA: NVIDIA GPU 1: GeForce GTX 950 (driver version 7.5.29, CUDA version 7.5, compute capability 5.2, 2048MB, 1918MB available, 2022 GFLOPS peak)
Sun May 29 14:00:52 2016 | | CUDA: NVIDIA GPU 2: GeForce GTX 750 Ti (driver version 7.5.29, CUDA version 7.5, compute capability 5.0, 2048MB, 1931MB available, 1388 GFLOPS peak)
Sun May 29 14:00:52 2016 | | OpenCL: NVIDIA GPU 0: GeForce GTX 950 (driver version 10.11.5 346.03.06f01, device version OpenCL 1.2, 2048MB, 1802MB available, 2022 GFLOPS peak)
Sun May 29 14:00:52 2016 | | OpenCL: NVIDIA GPU 1: GeForce GTX 950 (driver version 10.11.5 346.03.06f01, device version OpenCL 1.2, 2048MB, 1918MB available, 2022 GFLOPS peak)
Sun May 29 14:00:52 2016 | | OpenCL: NVIDIA GPU 2: GeForce GTX 750 Ti (driver version 10.11.5 346.03.06f01, device version OpenCL 1.2, 2048MB, 2048MB available, 87 GFLOPS peak)
Sun May 29 14:00:52 2016 | | OpenCL CPU: Intel(R) Xeon(R) CPU E5472 @ 3.00GHz (OpenCL driver vendor: Apple, driver version 1.1, device version OpenCL 1.2)
Sun May 29 14:00:52 2016 | | Processor: 8 GenuineIntel Intel(R) Xeon(R) CPU E5472 @ 3.00GHz [x86 Family 6 Model 23 Stepping 6]
Sun May 29 14:00:52 2016 | | OS: Mac OS X 10.11.4 (Darwin 15.4.0)

Now it thinks the 750TI is a pre-Fermi card.
stupid program...
At least it's numbering the GPUs correctly, but, it slowed the 950 by 20 secs over 6 mins.

The only way to run OpenCL on all three cards is to change out one of the cards.
I ran an ATI 6850 for a while, long enough to test a few OpenCL Apps.
It became Clear that OpenCL on nVidia GPUs is Broken in El Capitan 10.11.4. The same Apps work fine in Yosemite but slow and produce incorrect results in 10.11.4.
The CUDA Apps work Fine in El Capitan...in Real Macs.
The ATI/AMD Apps seem to work better in El Capitan and I was able to build a couple Apps that work slightly better with the VLARs. I still don't know how the Apps work on the newer Mac Pros.
I also built a new CPU App that works slightly better.

While running with just 2 CUDA cards it became apparent the 'Crash After Finish' happens less frequently, it might not happen at all with just One CUDA card. Going by those results, I'd say the 'Special' CUDA App should be posted to give the newer nVidia cards a working App in El Capitan. It will only work with GPUs that are Compute Code 3.2 and higher, but it's much better than the alternate. The older cards will have to keep using the older CUDA 65 App which runs the VLARs much slower, but does produce Correct results.
ID: 1791772 · Report as offensive
Profile jason_gee
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 24 Nov 06
Posts: 7489
Credit: 91,093,184
RAC: 0
Australia
Message 1791785 - Posted: 29 May 2016, 19:10:10 UTC - in response to Message 1791772.  

IMO Definitely needs some amount of wider testing (amongst people that know what they're doing at least). Probably best to check with Petri with respect to last emailed code how he'd feel about that. He PM'd that he's digging into the pulsefinding (which is what's needed for those Guppis), so not sure if that's still work in progress. I'd imagine he might be fine with marking it 'special' still, or perhaps beta or alpha.

Problem if making it look generic is people will run it on Pre cc3.2 nomatter how much you warn, so my part of folding the code into baseline with compute capability based dispatch becomes a bit more pressing (along with updating what he's already given me in Berkeley's repo first).

Most likely the final form of next generic stock will be clearer once more is known about the Pascal generation, and Cuda 8's only just out, so just warning that a lot could change very quickly if either of us stumble on some gotchas.
"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.
ID: 1791785 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1791812 - Posted: 29 May 2016, 20:34:56 UTC - in response to Message 1791785.  

...so just warning that a lot could change very quickly if either of us stumble on some gotchas.

Things may be getting better then right? I don't see how the gotcha could break what is already working ;-)
Maybe an OS 'update' may, but that is always possible.
Consider the current situation. The Mac nVidia LapTops have been producing bogus results for almost a year even though a solution has been available for around 4 months. Now the Desktops have problems with the recent OS. Should we wait another 6 months before releasing something that actually works? You can always update an App later, but Nothing will correct that Year of Incorrect results the LapTops have submitted.

I don't need to test something for months to tell if it produces valid results or in the case of the OpenCL App, Invalid results. For me, replacing something that doesn't work with something that does as soon as possible makes sense. The current CUDA 75 build produces very few Inconclusive results with a possible infrequent 'crash after finish' while printing the Correct results first. The current stock App produces nearly 100% Inconclusive results on the LapTops with the current OS, it's been that way for quite a while. How much longer should we wait to replace something that doesn't work, 6 months, a Year? You can always update the app later, all those bad results are unrecoverable.
ID: 1791812 · Report as offensive
Profile Raistmer
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 16 Jun 01
Posts: 6325
Credit: 106,370,077
RAC: 121
Russia
Message 1791826 - Posted: 29 May 2016, 21:06:04 UTC - in response to Message 1791812.  

The current stock App produces nearly 100% Inconclusive results on the LapTops with the current OS, it's been that way for quite a while. How much longer should we wait to replace something that doesn't work, 6 months, a Year? You can always update the app later, all those bad results are unrecoverable.

Few links to such hosts please.
ID: 1791826 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1791830 - Posted: 29 May 2016, 21:15:21 UTC - in response to Message 1791826.  
Last modified: 29 May 2016, 21:19:26 UTC

It's real easy, just look for any Mac nVidia LapTop that's running El Capitan.
This is the First LapTop at Beta, http://setiweb.ssl.berkeley.edu/beta/results.php?hostid=62183&offset=40
The others are similar.
I've posted links before, surely you saw them.
ID: 1791830 · Report as offensive
Profile Raistmer
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 16 Jun 01
Posts: 6325
Credit: 106,370,077
RAC: 121
Russia
Message 1791833 - Posted: 29 May 2016, 21:23:03 UTC - in response to Message 1791830.  

It's real easy, just look for any Mac nVidia LapTop that's running El Capitan.
This is the First LapTop at Beta, http://setiweb.ssl.berkeley.edu/beta/results.php?hostid=62183&offset=40
The others are similar.
I've posted links before, surely you saw them.


App on main behaves the same? I would like to see links for main (production app, not beta one).
ID: 1791833 · Report as offensive
Profile Raistmer
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 16 Jun 01
Posts: 6325
Credit: 106,370,077
RAC: 121
Russia
Message 1791835 - Posted: 29 May 2016, 21:28:37 UTC - in response to Message 1791833.  

It's real easy, just look for any Mac nVidia LapTop that's running El Capitan.
This is the First LapTop at Beta, http://setiweb.ssl.berkeley.edu/beta/results.php?hostid=62183&offset=40
The others are similar.
I've posted links before, surely you saw them.


App on main behaves the same? I would like to see links for main (production app, not beta one).

this particular host aborted work on main.
ID: 1791835 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1791837 - Posted: 29 May 2016, 21:31:46 UTC - in response to Message 1791835.  

You can start here, http://setiathome.berkeley.edu/forum_thread.php?id=78569&postid=1762177#1762177
Like I said, any Mac nVidia LapTop running Darwin 15.x.
ID: 1791837 · Report as offensive
Profile jason_gee
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 24 Nov 06
Posts: 7489
Credit: 91,093,184
RAC: 0
Australia
Message 1791839 - Posted: 29 May 2016, 21:33:20 UTC - in response to Message 1791812.  

Well those are questions for Petri and Eric (not my decisions).
Sadly I know little about the current other Mac apps, other than mine seems to work fine here, which is a (not very useful) sample size of one. Presuming the GPL requirements are met I don't see the obstacles you're perhaps seeing. Asking them would be IMO polite though.

Side Notes: I appreciate that not everyone works the same way I do, and that's a good thing, but doesn't pressure me to do other people's documentation & packaging or rush my own system or timetable for builds, testing, packages and releases. Thankfully there are some kind and helpful people at Lunatics and CA that help with a lot of that when the time is right for my own stuff. It's that collaborative (and time consuming) effort that makes a 'Release' as opposed to just posting builds on Forums.
"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.
ID: 1791839 · Report as offensive
Profile Raistmer
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 16 Jun 01
Posts: 6325
Credit: 106,370,077
RAC: 121
Russia
Message 1791843 - Posted: 29 May 2016, 21:37:26 UTC - in response to Message 1791837.  
Last modified: 29 May 2016, 21:42:44 UTC

You can start here, http://setiathome.berkeley.edu/forum_thread.php?id=78569&postid=1762177#1762177
Like I said, any Mac nVidia LapTop running Darwin 15.x.

Why you highlighting laptop nature of host. Non-laptops not affected with same driver/OS version?

Also, what driver versions affected?
I see 10.10.10 310.42.25f01 is bad one. What another?

EDIT: regarding why not to replace with smth better - you know procedure cause AFAIK some of your builds were at beta at least (released to main already btw? ).
You need to send binaries to Eric with descriptions and suggestions about corresponding plan_class they can work under.
And then to "ping" him until binaries will be deployed to beta :D
ID: 1791843 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1791850 - Posted: 29 May 2016, 21:50:56 UTC - in response to Message 1791843.  

The problems were first noticeable on the LapTops. The further back you go with the OS the less problems you find. The current OS, Darwin 15.x, seems to affect most of the LapTops with the Desktops being affected around 15.4.

Recent tests on My machine show nVidia OpenCL Apps compiled in Mavericks and El Capitan work fine in the last release of Yosemite but give bad results in Darwin 15.4 with GTX 750TI and 950 cards. I believe you are aware of a post on main about this? I think you were sent some files....
ID: 1791850 · Report as offensive
TBar
Volunteer tester

Send message
Joined: 22 May 99
Posts: 5204
Credit: 840,779,836
RAC: 2,768
United States
Message 1791854 - Posted: 29 May 2016, 22:00:16 UTC - in response to Message 1791839.  

Well those are questions for Petri and Eric (not my decisions).
Sadly I know little about the current other Mac apps, other than mine seems to work fine here, which is a (not very useful) sample size of one. Presuming the GPL requirements are met I don't see the obstacles you're perhaps seeing. Asking them would be IMO polite though.

Side Notes: I appreciate that not everyone works the same way I do, and that's a good thing, but doesn't pressure me to do other people's documentation & packaging or rush my own system or timetable for builds, testing, packages and releases. Thankfully there are some kind and helpful people at Lunatics and CA that help with a lot of that when the time is right for my own stuff. It's that collaborative (and time consuming) effort that makes a 'Release' as opposed to just posting builds on Forums.

Although I have become able to compile Apps that function, I know nothing about producing 'documentation' on code someone else wrote. I only compiled the App, I didn't write the code. My stance is if you want to know about the App you should ask the person that wrote it. I don't see how someone that didn't create the code can be asked about 'documentation'. So if someone asks me about about an App, you can find the answer here, https://setisvn.ssl.berkeley.edu/trac/browser/branches/sah_v7_opt
*nods head*
ID: 1791854 · Report as offensive
Profile Raistmer
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 16 Jun 01
Posts: 6325
Credit: 106,370,077
RAC: 121
Russia
Message 1791861 - Posted: 29 May 2016, 22:13:10 UTC - in response to Message 1791850.  

I believe you are aware of a post on main about this? I think you were sent some files....

Better to stop referring to my awareness. First of all I don't follow Mac issues too closely at all. I have lot of other things to remember and recall everyday, not to remember Mac issues. So if I ask smth - better just to try to cooperate (if ultimate goal is problem solving, not futile arguing ).
Also, all those rockets, sailors and fruits(?) tell nothing to me at all. OS X version/driver version. I never saw "Yosemite" in stderr output.
As you could know non-Windows binaries provider is Urs. If I need to intervene - then I need solid info what problem is, what affected range and so on. So far I see that we need plan_class correction to exclude OS X 15.x - right? What else?
ID: 1791861 · Report as offensive
Profile Raistmer
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 16 Jun 01
Posts: 6325
Credit: 106,370,077
RAC: 121
Russia
Message 1791865 - Posted: 29 May 2016, 22:19:15 UTC - in response to Message 1791861.  
Last modified: 29 May 2016, 22:19:40 UTC

Also, any similarity with AMD issue on OS X that Chris follows very good? Gaussians missing there - what pattern here (NV) if any?
ID: 1791865 · Report as offensive
Previous · 1 . . . 24 · 25 · 26 · 27 · 28 · 29 · 30 . . . 58 · Next

Message boards : Number crunching : I've Built a Couple OSX CUDA Apps...


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.