Intercept panic calls and replace them with aborts. #305
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Where "abort" currently is equivalent to
loop {}
, but we could try to do something better in the future.(Ideally we'd use a future variant of
OpKill
that works in all shaders, and ideally has the right semantics of leaving some kind of indication that there was an error in some shader invocation, but that might be asking for too much)The reason this is "WIP", even if it does work (see the test changes), is because, in order to defer errors from creating unsupported constants (mostly&panic::Location
) passed to panic entry-points, I had to turn them into zombies.So the tests only work because the panic calls are replaced with "abort"s, and the zombie constants never used.
From my discussion with @khyperia, we should be able to use zombies here (and in other places), if we can properly trackSpan
s for them, and I believe that's doable, but haven't gotten around to it.EDIT: that's all done, thanks to #311!