Skip to content

[mono][interp] Add vectorization for Vector4 - #87822

Merged
BrzVlad merged 8 commits into
dotnet:mainfrom
BrzVlad:feature-interp-vector4
Jul 5, 2023
Merged

[mono][interp] Add vectorization for Vector4#87822
BrzVlad merged 8 commits into
dotnet:mainfrom
BrzVlad:feature-interp-vector4

Conversation

@BrzVlad

Copy link
Copy Markdown
Member

And other vector of float improvements.

@ghost

Copy link
Copy Markdown

Tagging subscribers to this area: @BrzVlad, @kotlarmilos
See info in area-owners.md if you want to be subscribed.

Issue Details

And other vector of float improvements.

Author:BrzVlad
Assignees:-
Labels:

area-Codegen-Interpreter-mono

Milestone:-

BrzVlad added 8 commits July 5, 2023 09:51
Which is pretty much Vector<float>
The constructors receive each element as an argument. This is the same as `Vector128.Create` so we reuse that code. This ends up generating a MINT_SIMD_V128_I*_CREATE opcode which receives each element value as an argument.
Since it is common to instantiate Vector4 with constant values, add also support for tracking R4 values during optimizations. If all elements are constant, we generate instead a single MINT_SIMD_V128_LDC, which has the entire vector value embedded in the instruction stream.
It is not marked as simd type if the generic param is not valid (ex not primitive type). Future checks are not expecting this scenario and can potentially crash.
@BrzVlad
BrzVladforce-pushed the feature-interp-vector4 branch from ca4a6c5 to 941827dCompareJuly 5, 2023 06:51
@BrzVlad
BrzVlad merged commit 6d74424 into dotnet:mainJul 5, 2023
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@BrzVlad@vargaz