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

Fix DisableTier0Jit when multi-core JIT is enabled #23200

Merged
merged 1 commit into from
Mar 14, 2019

Conversation

kouvel
Copy link
Member

@kouvel kouvel commented Mar 12, 2019

  • With multi-core JIT, a method may be jitted before it is called, in which case the call counting entry would not already exist

- With multi-core JIT, a method may be jitted before it is called, in which case the call counting entry would not already exist
@kouvel kouvel added this to the 3.0 milestone Mar 12, 2019
@kouvel kouvel self-assigned this Mar 12, 2019
@kouvel kouvel requested a review from noahfalk March 12, 2019 06:18
Copy link
Member

@noahfalk noahfalk left a comment

Choose a reason for hiding this comment

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

lgtm

@kouvel
Copy link
Member Author

kouvel commented Mar 13, 2019

@dotnet-bot test Ubuntu x64 Formatting
test Ubuntu x64 Checked Innerloop Build and Test (Jit - TieredCompilation=0)
test Ubuntu x64 Checked Innerloop Build and Test
test Ubuntu x64 Checked CoreFX Tests

@kouvel kouvel merged commit 50d38a4 into dotnet:master Mar 14, 2019
@kouvel kouvel deleted the FixDisableTier0Jit branch March 14, 2019 20:51
picenka21 pushed a commit to picenka21/runtime that referenced this pull request Feb 18, 2022
)

- With multi-core JIT, a method may be jitted before it is called, in which case the call counting entry would not already exist

Commit migrated from dotnet/coreclr@50d38a4
Sign up for free to 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