On 26 October 2021 11:19:44 CEST, Richard Biener via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
>@@ -2010,6 +2010,7 @@ get_negative_load_store_type (vec_info *vinfo, > if (dump_enabled_p ()) > dump_printf_loc (MSG_MISSED_OPTIMIZATION, vect_location, > "negative step but alignment required.\n"); >+ *poffset = 0; > return VMAT_ELEMENTWISE; > *poffset = 0; > } I think you cannot really diagnose these, they would trigger a lot, in each early return, no? Or would we see that there are unreachable, non artificial stmts in the same block after a return? Somebody could experiment with diagnosing each and every DCEd stmt (!artificial, nondebug) but I would expect that hell breaks loose.. cheers,
