On 5/31/24 7:44 AM, Richard Biener wrote:
When vectorizing an early break loop with LENs (do we miss some
check here to disallow this?) we can end up deciding to insert
stmts after a GIMPLE_COND when doing SLP scheduling and trying
to be conservative with placing of stmts only dependent on
the implicit loop mask/len. The following avoids this, I guess
it's not perfect but it does the job fixing some observed
RISC-V regression.
* tree-vect-slp.cc (vect_schedule_slp_node): For mask/len
loops make sure to not advance the insertion iterator
beyond a GIMPLE_COND.
Note this patch may depend on others in the series. I don't think the
pre-commit CI tester is particularly good at handling that, particularly
if the other patches in the series don't have the tagging for the
pre-commit CI.
What most likely happened is this patch and only this patch was applied
against the baseline for testing.
There are (manual) ways to get things re-tested. I'm hoping Patrick and
Edwin automate that procedure relatively soon. Until that happens you
have to email patchworks...@rivosinc.com with a URL for the patch in
patchwork that you want retested.
Jeff
