Add predefined datatypes for FP8 formats #5882
Open
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.
Adds predefined datatypes for FP8 data in E4M3 and E5M2 formats
Does not add support for any native FP8 types; datatype conversions are performed in software
Important
Add predefined FP8 datatypes (E4M3 and E5M2) to HDF5 with software conversion support and update tests and documentation.
FLOAT_F8E4M3andFLOAT_F8E5M2toH5PredType.cppandH5PredType.h.H5T.candH5Tpublic.hto define FP8 E4M3 and E5M2 formats.h5util.candH5Tnative.cto handle FP8 conversions in software.H5LTparse.yandH5LTparse.cto include FP8 tokens.test_lite.c,dt_arith.c, anddtypes.c.h5dumpgentest.cto generate test files for FP8.CHANGELOG.mdto mention FP8 datatype limitations.predefinedDatatypes.dox.This description was created by
for 0523b99. You can customize this summary. It will automatically update as commits are pushed.