Skip to content
This repository was archived by the owner on Jan 23, 2023. It is now read-only.

Ensure that we check for implicit ivals for single argument intrinsics before the SIMDScalar handling.#25987

Merged
wtgodbe merged 1 commit into
dotnet:release/3.0from
tannergooding:backport-fix-25904
Aug 7, 2019
Merged

Ensure that we check for implicit ivals for single argument intrinsics before the SIMDScalar handling.#25987
wtgodbe merged 1 commit into
dotnet:release/3.0from
tannergooding:backport-fix-25904

Conversation

@tannergooding
Copy link
Copy Markdown
Member

Description

Certain intrinsic functions which took one argument, had an implicit immediate value , and were marked as SIMDScalar were not being handled correctly in codegen.

Customer Impact

Customers using functions qualifying under the above conditions would get invalid results in their program.

Regression?

Yes, as per the description.

Risk

Low. This just reorders the branch statements and the list of intrinsics that are impacted is small and well-defined: there are 102 intrinsics marked SIMDScalar and only 7 of them have both an implicit immediate value and take one argument.

…s before the SIMDScalar handling. (#25905)

* Ensure that we check for implicit ivals for single argument intrinsics before the SIMDScalar handling.

* Adding test template entries for the unary overloads of the Sse41.Round functions

* Regenerating the hardware intrinsic test templates.
@tannergooding tannergooding added this to the 3.0 milestone Aug 2, 2019
@tannergooding
Copy link
Copy Markdown
Member Author

CC. @CarolEidt, @AndyAyersMS

This is the backport of #25905 to release/3.0. This needs @MeiChin-Tsai's approval as well, correct?

@AndyAyersMS
Copy link
Copy Markdown
Member

This needs @MeiChin-Tsai's approval as well, correct?

At a minimum -- there may be more process now.

@danmoseley
Copy link
Copy Markdown
Member

At a minimum -- there may be more process now.

It needs to get ok from Tactics on Tues.

@danmoseley
Copy link
Copy Markdown
Member

Approved by tactics for 3.0, @wtgodbe or @Anipik will merge when branch opens for preview 9.

@danmoseley
Copy link
Copy Markdown
Member

(assuming CI is green)

@wtgodbe
Copy link
Copy Markdown
Member

wtgodbe commented Aug 7, 2019

Branch is open, merging

@wtgodbe wtgodbe merged commit b4a56b0 into dotnet:release/3.0 Aug 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants