Skip to content

Conversation

@bashbaug
Copy link
Contributor

Instead of adding aliases to cl_mem_migration_flags and associated enums, restrict the clEnqueueMigrateMemINTEL API to OpenCL 1.2 or newer, which satisfies all current use-cases.

If needed, the aliases can be re-introduced at a later date, since adding them does not change the ABI.

See related header file PR: KhronosGroup/OpenCL-Headers#65

Instead of adding aliases to cl_mem_migration_flags and associated
enums, restrict the clEnqueueMigrateMemINTEL API to OpenCL 1.2 or
newer, which satisfies all current use-cases.

If needed, the aliases can be re-introduced at a later date, since
adding them does not change the ABI.
Copy link
Contributor

@alycm alycm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, sorry that this has been sat so long.

@alycm alycm merged commit b3d030c into KhronosGroup:master Jun 8, 2020
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.

2 participants