https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105275

--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
Since this was a costing change I wonder if we identified the code change
responsible and thus have a testcase?  I realize that for maximum assurance
one would need to have a debug counter for switching the patch on/off to
have it apply more selectively (possibly per SLP attempt rather than
per cost hook invocation which would be even more tricky to do).

Feeding another parameter to the hook via a new flag in the vinfo might
be possible (and set that from a dbg_cnt call) for example.

Reply via email to