[PyTorch] Remove some direct calls to PyTorch extensions in Float8Tensor
#1137
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.
Description
When
Float8Tensor
launches TE kernels, it directly calls the PyTorch extensions rather than using the Python wrapper functions inte.pytorch.cpp_extensions
. This is because the Python wrapper functions required passing inFP8TensorMeta
objects. #1083 changed the APIs so theFP8TensorMeta
s are optional. This PR takes advantage of these new APIs, which also has the effect of registering FP8 casts with TorchScript.Type of change
Changes
tex.cast_to_fp8
andtex.cast_from_fp8
calls inFloat8Tensor
withcpp_extensions
wrappersChecklist: