Skip to content

Conversation

@petrex
Copy link
Contributor

@petrex petrex commented Oct 10, 2019

Goal : Stick to code_object_v2 for LLVM AMDGPU backend at this moment.

I am taking the action item to enable code_object_v3 when it's ready and validated.

@masahi
Copy link
Member

masahi commented Oct 11, 2019

Does v2 work on recent LLVM?

@petrex
Copy link
Contributor Author

petrex commented Oct 11, 2019

code_object_v2 is still supported, although this is not the default.
See https://llvm.org/docs/AMDGPUUsage.html

A side note: we are sorting out issue w.r.t to code_object_v3. At this moment, code_object_v2 would be a safer choice.

@masahi masahi merged commit 15ae978 into apache:master Oct 11, 2019
@t-vi
Copy link
Contributor

t-vi commented Oct 11, 2019

Just to add some note about the impact: This fixes the cross-thread reductions, which were broken because the code v3 objects seem to loose the fixed group segment ("shared memory") property, and reading out of bounds returns 0.

@petrex
Copy link
Contributor Author

petrex commented Oct 11, 2019

yes, this is one of the motivations behind the fix. Thanks for the confirmation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants