> This is the patch I have committed after resolving a conflict (and > another round of bootstrapping and testing). The ChangeLog is still > the same. > > The previous version of the patch (but with tree code already > converted to an enum), the aggregate jump functions together with > enlarged inlining predicates increased Mozilla Firefox LTO WPA memory > consumption by 1.2% (6775287 kb -> 6855035 kb as measured by > maxmem2.sh). On Monday I will make another measurement with jump > functions completely switched off.
Thanks! I did bit of static analysis on Mozilla, we increase number of predicated instructions by about 30% that is quite good. We seem to be weaker on actually using the predicates however, about 1% of inline decisions lead to using those predicates. I guess there is room for improvements in jump functions construction/propagation, right? :) Looking at the dumps we get some quit interesting matches like memset call when the destination argument is known to be zero already etc. Honza
