On 22 March 2023 13:29:52 CET, Richard Biener via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
>The alternative would be to change last_stmt, explicitely introducing >last_nondebug_stmt. I remember we chickened out and made last_stmt >conservative here but not anticipating the compile-time issues this >creates. I count 227 last_stmt and 12 last_and_only_stmt uses. In https://inbox.sourceware.org/gcc-help/20211121010713.1452267f@nbbrfq/ i asked if maybe ---8<--- 1) last_stmt wouldn't it be more efficient if tree-cfg.c:: last_stmt() would gimple_seq_last_nondebug_stmt (bb_seq (bb)) ? That would set stmt=NULL only after the loop it seems..
