On Tue, Aug 23, 2016 at 01:40:01PM -0700, Paul Turner wrote: > Independent of this patch: > When we initially introduced load scaling, it was ~uniform on every > value. Most of the current pain has come from, and will continue to > come from, that with v2 of the load-tracking this is no longer the > case. We have a massive number of scaled and unscaled inputs floating > around, many of them derived values (e.g. source_load above) which > require chasing. > > I propose we simplify this.
Yes please... I had been thinking of trying to use sparse to give the different FP scales different types, but gave up real quick on that.
