Skip to content

Rename ConvertFToTF32INTEL to RoundFToTF32INTEL #8846

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from

Conversation

MrSidims
Copy link
Contributor

@MrSidims MrSidims commented Mar 28, 2023

Extension name will be preserved for a while for binary compatibility.

There is not public spec change yet, but it has to be done ASAP

It's a cherry-pick of KhronosGroup/SPIRV-LLVM-Translator#1913

Extension name will be preserved for a while for binary compatibility.

There is not public spec change yet, but it has to be done ASAP

Signed-off-by: Sidorov, Dmitry <dmitry.sidorov@intel.com>
@MrSidims MrSidims requested a review from a team as a code owner March 28, 2023 23:14
@MrSidims MrSidims temporarily deployed to aws March 29, 2023 05:07 — with GitHub Actions Inactive
Signed-off-by: Sidorov, Dmitry <dmitry.sidorov@intel.com>
@MrSidims MrSidims temporarily deployed to aws March 29, 2023 11:41 — with GitHub Actions Inactive
@MrSidims MrSidims temporarily deployed to aws March 29, 2023 12:33 — with GitHub Actions Inactive
@MrSidims MrSidims temporarily deployed to aws March 30, 2023 13:56 — with GitHub Actions Inactive
@MrSidims MrSidims temporarily deployed to aws March 30, 2023 13:57 — with GitHub Actions Inactive
@@ -101,6 +101,7 @@ enum InternalCapability {
ICapFPArithmeticFenceINTEL = 6144,
ICapGlobalVariableDecorationsINTEL = 6146,
ICapabilityComplexFloatMulDivINTEL = 6414,
ICapabilityTensorFloat32RoundingINTEL = 6425,
ICapabilityTensorFloat32ConversionINTEL = 6425,
Copy link
Contributor

@asudarsa asudarsa Mar 31, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

will the two enums having same value cause issues here in expected behavior? Also, may be a TODO here? Thanks

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh, it's a cherry-pick mistake

Copy link
Contributor

@asudarsa asudarsa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. Only one correction needed. Please address that before merging. Thanks

@MrSidims
Copy link
Contributor Author

MrSidims commented Apr 2, 2023

Probably we don't need this patch ASAP here, @dkhaldi please confirm

@MrSidims
Copy link
Contributor Author

MrSidims commented Apr 3, 2023

Closing as we don't need it here ASAP and can wait for the pulldown

@MrSidims MrSidims closed this Apr 3, 2023
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