SVE: Reuse ptrue value instead of rematerializing it everytime
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- compilers
Research direction
Start from the SVE code-generation path that emits the ptrue instructions shown in the issue and trace how predicate values are represented across uses and call boundaries. Define completion as reusing compatible ptrue values without changing predicate types or generated-code semantics, then validate the resulting assembly and relevant compiler tests.
Written by the indexing model from the issue text.
Description
Noticed the below piece of code, where we materialize p0 before every usage instead of just saving it and reusing it.
G_M34563_IG04: ; bbWeight=4, gcrefRegs=0000 {}, byrefRegs=0000 {}, byref, isz
ldp q18, q19, [x0]
ptrue p0.d
fabs z18.d, p0/m, z18.d
fadd v0.2d, v0.2d, v18.2d
ptrue p0.d
fabs z18.d, p0/m, z19.d
fadd v0.2d, v0.2d, v18.2d
ldp q18, q19, [x0, #0x20]
ptrue p0.d
fabs z18.d, p0/m, z18.d
fadd v0.2d, v0.2d, v18.2d
ptrue p0.d
fabs z18.d, p0/m, z19.d
fadd v0.2d, v0.2d, v18.2d
ldp q18, q19, [x0, #0x40]
ptrue p0.d
fabs z18.d, p0/m, z18.d
fadd v0.2d, v0.2d, v18.2d
ptrue p0.d
fabs z18.d, p0/m, z19.d
fadd v0.2d, v0.2d, v18.2d
ldp q18, q19, [x0, #0x60]
ptrue p0.d
fabs z18.d, p0/m, z18.d
fadd v0.2d, v0.2d, v18.2d
ptrue p0.d
fabs z18.d, p0/m, z19.d
fadd v0.2d, v0.2d, v18.2d
add x0, x0, #128
sub x1, x1, #16
cmp x1, #16
bhs G_M34563_IG04
Either we can track the number of usages (probably count separate groups that do not cross call boundary) and then store them as LclVar. We could have a dedicated predicate register to represent ptrue value, but we would need to have different registers depending on the type (ptrue p0.b and ptrue p0.d are different).
- Dominant language
- C#
- Stars
- 18.3k
- Forks
- 5.6k
- PR merge metrics
- PR metrics pending
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dotnet/runtime
-
agentic-workflows untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
area-System.Reflection blocking-clean-ci-optional Known Build Error os-mac-os-x untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
area-CodeGen-coreclr untriaged
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
agentic-workflows untriaged
Difficulty 1/5 Under an hour Newbie friendliness 78/100
-
area-VM-meta-mono untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
:watch: Not Triaged 11.0 fundamentals/subsvc
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
dotnet/AspNetCore.Docs#37699 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SubtitleEdit/subtitleedit#15108 · 1 comment ·
-
area/docs-content Bug pulumi/docs
Difficulty 1/5 1-3 hours Newbie friendliness 94/100
-
Create parent directories only after the containment check in InstallHelper.TryExtractToDirectory Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PowerShell/PSResourceGet#2056 ·