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

JIT: update lvaGrabTemp for new minopts/debug ref counting approach #19351

Merged
merged 1 commit into from
Aug 8, 2018

Conversation

AndyAyersMS
Copy link
Member

If the jit has started normal ref counting and is in minopts or debug,
set all new temps to be implicitly referenced by default.

Closes #19346.

If the jit has started normal ref counting and is in minopts or debug,
set all new temps to be implicitly referenced by default.

Closes #19346.
@AndyAyersMS
Copy link
Member Author

@BruceForstall ptal
cc @dotnet/jit-contrib

Will be further extended by #19345, but that is not quite ready for prime time.

@dotnet-bot test Windows_NT x64 Checked Build and Test

@AndyAyersMS
Copy link
Member Author

Trying to trigger PRI1 again...

@dotnet-bot test Windows_NT x64 Build and Test

@AndyAyersMS
Copy link
Member Author

@dotnet-bot retest Ubuntu x64 Checked CoreFX Tests


unsigned tempNum = lvaCount;
lvaTable[tempNum].lvType = TYP_UNDEF; // Initialize lvType, lvIsTemp and lvOnFrame

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: I think a comment that applies to multiple lines should be above the first line (though I realize this was already here).

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll fix this as part of #19345.

@AndyAyersMS
Copy link
Member Author

@dotnet/dnceng CoreCLR ARM CI seems like it may be having troubles...?
cc @jashook

@BruceForstall
Copy link
Member

CoreCLR ARM CI seems like it may be having troubles...?

Our Windows arm64 machines all appear "offline" to Jenkins.

cc @RussKeldorph

@AndyAyersMS AndyAyersMS merged commit 585cd36 into dotnet:master Aug 8, 2018
@AndyAyersMS AndyAyersMS deleted the Fix19346 branch August 8, 2018 20:05
@MattGal
Copy link
Member

MattGal commented Aug 8, 2018

@BruceForstall I'm not sure which Windows ARM64 machines you're referencing, but we're definitely experiencing DNS issues in the on-premises OSX machines, which are co-located with the ARM64 machines and likely to experience the same problem. I'll update if I get more info, @JpratherMS FYI.

@BruceForstall
Copy link
Member

The ARM64-AMD-xxx machines are the ones. @jashook / @RussKeldorph and I manage those.

@MattGal
Copy link
Member

MattGal commented Aug 8, 2018

I haven't actually used these machines before, but I checked out 011 and noticed that while DNS resolution did work the OS on it expired over a month ago. This could be part of the problem, automatic login may be failing due to a blocking dialog about windows expiring?

@sdmaclea
Copy link

sdmaclea commented Aug 9, 2018

These were also failing w/o this patch in jitMinOpts=1

JIT/jit64/regress/vsw/575343/test2/test2.sh
JIT/Regression/CLR-x86-JIT/V1-M11-Beta1/b44946/b44946/b44946.sh
JIT/Regression/CLR-x86-JIT/V2.0-RTM/b598031/test2/test2.sh
JIT/Regression/CLR-x86-JIT/v2.1/b569942/b569942/b569942.sh
JIT/Regression/CLR-x86-JIT/v2.1/b608198/b608198/b608198.sh
JIT/Regression/VS-ia64-JIT/V2.0-Beta2/b333008/b333008/b333008.sh

They have been resolved also.

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.

5 participants