Skip to content

Should /debug+ be enabled by default for /optimize builds? #26484

Open

Description

/debug+ was a flag intended to stop optimizations where they may destroy locals. However, it only takes effect when a local crosses the statement boundary -- temps and other unobservable locals are still stack-optimized. Stack locals that live past a single statement ("long lived") tend to be pretty rare as a percentage of total stack-schedulable locals (most locals that can be stack scheduled are temps). If this optimization doesn't have a large effect, maybe it's worth turning off by default?

cc @VSadov

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions