https://community.intel.com/t5/OpenCL-for-CPU/Address-bits-CPU-32-GPU-64/m-p/1023174#M3377 <P>I was playing around with the new 2014 Intel OpenCL SDK, and I noticed that when compiling for Win32, CL_DEVICE_ADDRESS_BITS query returned 32 for the CPU, but 64 for the GPU. &nbsp;That seems quite odd to me, is that correct? &nbsp;If I compile for x64, then both return 64, which isn't too strange.</P> <P>&nbsp;</P> <P>Also, is there any good reason why my CPU's CL_DEVICE_NAME starts with six spaces, e.g., "&nbsp; &nbsp; &nbsp; Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz"? &nbsp;My GPU's CL_DEVICE_NAME starts immediately with "Intel(R)...".</P> Mon, 26 May 2014 01:33:06 GMT Sean_S_3 2014-05-26T01:33:06Z https://community.intel.com/t5/OpenCL-for-CPU/Address-bits-CPU-32-GPU-64/m-p/1023174#M3377 <P>I was playing around with the new 2014 Intel OpenCL SDK, and I noticed that when compiling for Win32, CL_DEVICE_ADDRESS_BITS query returned 32 for the CPU, but 64 for the GPU. &nbsp;That seems quite odd to me, is that correct? &nbsp;If I compile for x64, then both return 64, which isn't too strange.</P> <P>&nbsp;</P> <P>Also, is there any good reason why my CPU's CL_DEVICE_NAME starts with six spaces, e.g., "&nbsp; &nbsp; &nbsp; Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz"? &nbsp;My GPU's CL_DEVICE_NAME starts immediately with "Intel(R)...".</P> Mon, 26 May 2014 01:33:06 GMT https://community.intel.com/t5/OpenCL-for-CPU/Address-bits-CPU-32-GPU-64/m-p/1023174#M3377 Sean_S_3 2014-05-26T01:33:06Z