add nvptx_target_feature and use unaligned barrier #1805
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.
_syncthreads
(the CUDA name) in favor of new_barrier_sync
(NVPTX namebarrier.sync
).barrier.sync
instruction is equivalent tobarrier.sync.aligned
prior tosm_70
, and will lead to errors/deadlock if passes (such as MIRJumpThreading
) lose the aligned property.convergent
attribute (and becauseconvergent
does not preserve alignment, which can be broken by inlining), we cannot pre 8000 vent loss of alignment, and thus we require target featuresm_70
. In short, we cannot prevent miscompilation of aligned barriers without hard-to-specify preconditions.This requires rust-lang/rust#138689 (for
nvptx_target_feature
) and fixes rust-lang/rust#137086.