public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/108685] [10/11/12/13 Regression] ICE in verify_loop_structure, at cfgloop.cc:1748 since r13-2388-ga651e6d59188da
Date: Wed, 15 Feb 2023 16:14:17 +0000	[thread overview]
Message-ID: <bug-108685-4-4NlXVHDKWk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108685-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Though, we have such code already:
      if (broken_loop)
        {
          int i;
          for (i = fd->collapse; i < fd->ordered; i++)
            {
              tree type = TREE_TYPE (fd->loops[i].v);
              tree this_cond
                = fold_build2 (fd->loops[i].cond_code, boolean_type_node,
                               fold_convert (type, fd->loops[i].n1),
                               fold_convert (type, fd->loops[i].n2));
              if (!integer_onep (this_cond))
                break;
            }
          if (i < fd->ordered)
            {
              cont_bb
                = create_empty_bb (EXIT_BLOCK_PTR_FOR_FN (cfun)->prev_bb);
              add_bb_to_loop (cont_bb, l1_bb->loop_father);
              gimple_stmt_iterator gsi = gsi_after_labels (cont_bb);
              gimple *g = gimple_build_omp_continue (fd->loop.v, fd->loop.v);
              gsi_insert_before (&gsi, g, GSI_SAME_STMT);
              make_edge (cont_bb, l3_bb, EDGE_FALLTHRU);
              make_edge (cont_bb, l1_bb, 0);
              l2_bb = create_empty_bb (cont_bb);
              broken_loop = false;
            }
        }
and at least when the outermost for (;;) is missing, it works fine.

  parent reply	other threads:[~2023-02-15 16:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-06 18:50 [Bug c/108685] New: [13 Regression] ICE in verify_loop_structure, at cfgloop.cc:1748 gscfq@t-online.de
2023-02-06 20:20 ` [Bug middle-end/108685] " pinskia at gcc dot gnu.org
2023-02-07 14:06 ` rguenth at gcc dot gnu.org
2023-02-10  9:05 ` [Bug middle-end/108685] [13 Regression] ICE in verify_loop_structure, at cfgloop.cc:1748 since r13-2388-ga651e6d59188da marxin at gcc dot gnu.org
2023-02-15 13:41 ` [Bug middle-end/108685] [10/11/12/13 " jakub at gcc dot gnu.org
2023-02-15 15:15 ` jakub at gcc dot gnu.org
2023-02-15 16:14 ` jakub at gcc dot gnu.org [this message]
2023-02-21 12:50 ` rguenth at gcc dot gnu.org
2023-03-16 17:32 ` jakub at gcc dot gnu.org
2023-03-17  8:00 ` cvs-commit at gcc dot gnu.org
2023-03-17  8:29 ` [Bug middle-end/108685] [10/11/12 " jakub at gcc dot gnu.org
2023-03-19  5:31 ` cvs-commit at gcc dot gnu.org
2023-03-20 10:30 ` [Bug middle-end/108685] [10/11 " jakub at gcc dot gnu.org
2023-05-02 20:15 ` cvs-commit at gcc dot gnu.org
2023-05-03 10:37 ` [Bug middle-end/108685] [10 " jakub at gcc dot gnu.org
2023-05-03 15:22 ` cvs-commit at gcc dot gnu.org
2023-05-04  7:24 ` jakub at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-108685-4-4NlXVHDKWk@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).