Skip to content
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

OSR variants may not report pinned locals as pinned #67668

Closed
jakobbotsch opened this issue Apr 6, 2022 · 3 comments · Fixed by #67680
Closed

OSR variants may not report pinned locals as pinned #67668

jakobbotsch opened this issue Apr 6, 2022 · 3 comments · Fixed by #67680
Labels
area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI
Milestone

Comments

@jakobbotsch
Copy link
Member

Description

See here: #66983 (comment)

Reproduction Steps

Trigger OSR inside the loops in System.Globalization.CompareInfo.IndexOfOrdinalHelper.

Expected behavior

The OSR variant keeps pinning variables that were pinned in tier-0.

Actual behavior

The OSR variant does not report these locals as pinned anymore.

Regression?

No response

Known Workarounds

No response

Configuration

No response

Other information

No response

@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged New issue has not been triaged by the area owner label Apr 6, 2022
@dotnet-issue-labeler
Copy link

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

@jakobbotsch jakobbotsch added the area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI label Apr 6, 2022
@ghost
Copy link

ghost commented Apr 6, 2022

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

Issue Details

Description

See here: #66983 (comment)

Reproduction Steps

Trigger OSR inside the loops in System.Globalization.CompareInfo.IndexOfOrdinalHelper.

Expected behavior

The OSR variant keeps pinning variables that were pinned in tier-0.

Actual behavior

The OSR variant does not report these locals as pinned anymore.

Regression?

No response

Known Workarounds

No response

Configuration

No response

Other information

No response

Author: jakobbotsch
Assignees: -
Labels:

area-CodeGen-coreclr, untriaged

Milestone: -

@AndyAyersMS
Copy link
Member

Thanks. Looks like what I suspected, the OSR method sees the locals as pinned but also unreferenced... I think we just need to add an implicit reference.

;* V06 loc0         [V06    ] (  0,  0   )    long  ->  zero-ref   
;* V07 loc1         [V07    ] (  0,  0   )   byref  ->  zero-ref    pinned
;* V08 loc2         [V08    ] (  0,  0   )    long  ->  zero-ref   
;* V09 loc3         [V09    ] (  0,  0   )   byref  ->  zero-ref    pinned

@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label Apr 7, 2022
@ghost ghost removed the in-pr There is an active PR which will close this issue when it is merged label Apr 7, 2022
@jeffhandley jeffhandley removed the untriaged New issue has not been triaged by the area owner label May 6, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Jun 5, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants