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

Handle a restored double Interval at block boundary #16511

Merged
merged 1 commit into from
Feb 23, 2018

Conversation

CarolEidt
Copy link

During the process of freeing registers that are no longer live at the start of a new block, we may restore a 'previousInterval'. If that is a double (and the freed interval was float), we need to skip the next float.

During the process of freeing registers that are no longer live at the start of a new block, we may restore a 'previousInterval'. If that is a double (and the freed interval was float), we need to skip the next float.
@CarolEidt
Copy link
Author

@dotnet/jit-contrib PTAL
This fixes DevDiv bug 541653

@CarolEidt
Copy link
Author

Since the code changed is exclusively under #ifdef _TARGET_ARM_, I'm going to simply ignore failures on other targets unless they happen to be in the newly added test (which so far they aren't).

@CarolEidt CarolEidt merged commit 88abf49 into dotnet:master Feb 23, 2018
@CarolEidt CarolEidt deleted the FixDD541653 branch July 16, 2018 19:15
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.

2 participants