Unreasonable STARS/IRDB memory usage in move_globals
Recent commits of move_globals integrate STARS to enable the annotations that allow move_globals to be more accurate. However, memory usage is a problem. As a point of comparison, I looked at memory usage across other $PSZ steps. Here's some results:
For AWS:
fill_in_cfg: 0.89 gb
fill_in_indtargs: 1.04 gb
fix_calls: 1.04 gb
p1: 1.44 gb
move_globals (without stars): 1.44 gb
STARS/IDA: 1.24 gb
---
move_globals (with stars): 8.51 gb
Postgres has similar results, with move_globals+STARS/IRDB taking 10.4gb of memory.
I added code in move_globals to disable STARS usage for comparison purposes. I have to do a delivery this week of the VGT toolchain, and I'd like to include STARS, but with current memory usage that seems infeasible. If @clc can address this quickly, perhaps it can still make the delivery. This will likely be the last delivery of a built/working VGT. Though, there will still be a source delivery of the VGT later in the month.