Skip to content

Conversation

@9prady9
Copy link
Member

@9prady9 9prady9 commented Jul 9, 2020

Description

Enable confidence connected components function in OpenCL backend.

Changes to Users

The users can use confidence connected components in OpenCL backend from now on.

Checklist

  • Rebased on latest master
  • Code compiles
  • Tests pass
  • [ ] Functions added to unified API
  • [ ] Functions documented

@9prady9 9prady9 added the OpenCL label Jul 9, 2020
@9prady9 9prady9 requested a review from umar456 July 9, 2020 10:42
Without the extra barrier sync towards end of barrierOR function
after reading the reduction result, the caller's loop if any is
going into infinite loop occasionally which is in turn randoms hangs.

This doesn't seem to be an issue on non-nvidia hardware. Hence, we are
conditionally adding the extra barrier sync conditionally for nvidia
platform.
@9prady9 9prady9 changed the title Fix opencl barrierOR fn in confidence connected opencl kernel Fix barrierOR fn in confidence connected opencl kernel Jul 9, 2020
@9prady9 9prady9 added this to the 3.8.0 milestone Jul 9, 2020
@9prady9 9prady9 merged commit 64855cb into arrayfire:master Jul 10, 2020
@9prady9 9prady9 deleted the improv_ccc branch July 10, 2020 03:30
@9prady9 9prady9 modified the milestones: 3.8.0, 3.7.3 Aug 7, 2020
9prady9 added a commit that referenced this pull request Aug 17, 2020
* Fix barrierOR fn in confidence connected opencl kernel

Without the extra barrier sync towards end of barrierOR function
after reading the reduction result, the caller's loop if any is
going into infinite loop occasionally which is in turn randoms hangs.

This doesn't seem to be an issue on non-nvidia hardware. Hence, we are
conditionally adding the extra barrier sync conditionally for nvidia
platform.

* Add the hardware check comparison

(cherry picked from commit 64855cb)
umar456 pushed a commit that referenced this pull request Sep 9, 2020
* Fix barrierOR fn in confidence connected opencl kernel

Without the extra barrier sync towards end of barrierOR function
after reading the reduction result, the caller's loop if any is
going into infinite loop occasionally which is in turn randoms hangs.

This doesn't seem to be an issue on non-nvidia hardware. Hence, we are
conditionally adding the extra barrier sync conditionally for nvidia
platform.

* Add the hardware check comparison

(cherry picked from commit 64855cb)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants