Results 1 to 2 of 2

Thread: Intel Iris Pro problems (Apple MacBook Pro)

  1. #1

    Intel Iris Pro problems (Apple MacBook Pro)

    I've been testing OpenCL v1.2 on an Apple MacBook Pro and have encountered 2 (so far) issues where the Iris Pro behavior seems to be incorrect.
    (1) When sampling an image, the Iris Pro yields a different interpolation to the clamped values. (Clamping specification: CLK_NORMALIZED_COORDS_FALSE | CLK_ADDRESS_CLAMP | CLK_FILTER_LINEAR)
    (2) When using atomic_inc in a kernel the Iris Pro triggers a call to __pthread_kill from clWaitForEvents

    The first issue was awkward (it causes unit tests to fail). The second issue is untenable (it causes unit testing to crash).

    Is there a way to work around this issue other than excluding the Iris Pro?

    P.S. Hardware specifics:
    MacBook Pro (Retina, 15-inch, Mid 2014)
    2.8 GHz Intel Core i7
    NVIDIA GeForce GT 750M 2048 MB
    Intel Iris Pro 1536 MB
    Framework is what Apple provides:
    /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/System/Library/Frameworks/OpenCL.framework

  2. #2
    Update: Additionally, a declaration of a local variable within kernel code results in a compile failure. (Works as it should for Core i7 and GT 750M.)

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Proudly hosted by Digital Ocean