Hi Jeff,
> What I would suggest, as you find things that are potential improvements
> to be made, try to reduce to a sensible testcase, then get a bug filed.
> That way multiple engineers can see what you're finding and potentially
> contribute.
> If/when you file those bugs, make them blockers for bug #26163. 26163 is
> a tracker for issues found in spec. You might also want to review any
> bugs blocking 26163. The most interesting ones will have a testcase
> attached, those which are "N% slowdown in XXX" aren't nearly as useful.
Thanks a lot for the guidance.
I'll start by going through the current status of bug #26163 and the bugs
blocking it, and dig into the SPEC CPU2017 hot spots to see whether
there are any remaining optimization opportunities.
Best regards,
Yaduo
