On 6/10/24 12:27 PM, Philipp Tomsich wrote:
This change is what I briefly hinted as "the complete solution" that
we had on the drawing board when we briefly talked last November in
Santa Clara.
I haven't any recollection of that part of the discussion, but I was a
bit frazzled as you probably noticed.
We have looked at all of SPEC2017, especially for coverage (i.e.,
making sure we see a significant number of uses of the transformation)
and correctness. The gcc_r and parest_r components triggered in a
number of "interesting" ways (e.g., motivating the case of
load-elimination). If it helps, we could share the statistics for how
often the pass triggers on compiling each of the SPEC2017 components?
Definitely helpful. I may be able to juggle some priorities internally
to lend a larger hand on testing and helping move this forward. It's an
area we're definitely interested in.
Jeff
