Skip to content

Conversation

@RossBrunton
Copy link
Contributor

This device info is used to specify whether a given device can validate
arguments passed to a kernel when it is launched. This also updates the
spec to specify that if this value is not set, then running a kernel
with invalid arguments is UB.

This does not imply any behavior changes in adapters themselves; they
already UB-ed anyway. This just writes it into the spec and makes
some conformance tests not fail them for it.

This device info is used to specify whether a given device can validate
arguments passed to a kernel when it is launched. This also updates the
spec to specify that if this value is not set, then running a kernel
with invalid arguments is UB.

This does not imply any behavior changes in adapters themselves; they
already UB-ed anyway. This just writes it into the spec and makes
some conformance tests not fail them for it.
@RossBrunton
Copy link
Contributor Author

More internal discussion and it looks like a device info property is probably overkill and we should just make it always UB (and have OpenCL report an error to some log somewhere).

@jchlanda
Copy link
Contributor

More internal discussion and it looks like a device info property is probably overkill and we should just make it always UB (and have OpenCL report an error to some log somewhere).

Does it mean that this PR still needs to be reviewed, or can it be closed converted to a draft?

@RossBrunton
Copy link
Contributor Author

#17962

Replaced by this. Sorry about all the pings!

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