19434, "bradcray", "Is the localizeGlobals optimization doing us any good?", "2022-03-12T17:27:04Z"
I'd completely forgotten about the localizeGlobals pass of the compiler
until running into it last night while working on optimizing enum
conversions in a branch that uses tuples to represent them. This was
originally introduced for the sake of the XMT compiler and architecture.
Is it still generating value for us? For all types?
This issue proposes disabling the pass to see the effect, and if it hurts
in some cases, working harder to distinguish cases where it should
be applied vs. where it shouldn't.