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.

Sign up for GitHub

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

Jump to bottom

Add an option to not generate precise GC info #88811

Closed
wants to merge 2 commits into from
Closed

Add an option to not generate precise GC info #88811

wants to merge 2 commits into from

Commits on Jul 13, 2023

  1. Add an option to not generate precise GC info 

    Revived dotnet#75817 with a small change.

Follow up to dotnet#75803.

If enabled, conservative GC stack scanning will be used and metadata related to GC stack reporting will not be generated. The generated executable file will be smaller, but the GC will be less efficient (garbage collection might take longer and keep objects alive for longer periods of time than usual).

Saves 4.4% in size on a Hello World. Saves 6.7% on Stage 1. I'll take that.

The main difference from the previous PR is that I'm no longer dropping GC info on `UnmanagedCallersOnly` methods and that seems to be enough to make Smoke tests pass.
    @MichalStrehovsky
    MichalStrehovsky committed Jul 13, 2023
    Configuration menu
    Copy the full SHA
    2b09f34 View commit details
    Browse the repository at this point in the history

  2. Temporary test changes

    @MichalStrehovsky
    MichalStrehovsky committed Jul 13, 2023
    Configuration menu
    Copy the full SHA
    035137e View commit details
    Browse the repository at this point in the history