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

[mbr] [wasm] Don't automatically turn off inlining #47246

Merged
merged 1 commit into from
Jan 21, 2021

Conversation

lambdageek
Copy link
Member

Instead of turning off inlining whenever ENABLE_METADATA_UPDATE is defined in
the code, only turn it off when MONO_METADATA_UPDATE is set in the environment.

Update the browser MBR sample to use the env var

@ghost
Copy link

ghost commented Jan 20, 2021

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

Issue Details

Instead of turning off inlining whenever ENABLE_METADATA_UPDATE is defined in
the code, only turn it off when MONO_METADATA_UPDATE is set in the environment.

Update the browser MBR sample to use the env var

Author: lambdageek
Assignees: -
Labels:

area-VM-meta-mono

Milestone: -

Instead of turning off inlining whenever ENABLE_METADATA_UPDATE is defined in
the code, only turn it off when MONO_METADATA_UPDATE is set in the environment.

Update the browser MBR sample to use the env var
Copy link
Contributor

@CoffeeFlux CoffeeFlux left a comment

Choose a reason for hiding this comment

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

Are you planning to re-run the benchmarks with this PR to see if it solves the regressions?

@lambdageek
Copy link
Member Author

lambdageek commented Jan 20, 2021

Are you planning to re-run the benchmarks with this PR to see if it solves the regressions?

I wasn't going to measure this one - not turning off inlining unless we need was a TODO regardless. It's only going to improve the wasm perf - jit and desktop interp need additional investigation.

@lambdageek lambdageek merged commit c0f67b2 into dotnet:master Jan 21, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Feb 20, 2021
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.

3 participants