public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/109410] [13 Regression] ICE: verify_flow_info failed
Date: Sun, 23 Apr 2023 03:58:56 +0000	[thread overview]
Message-ID: <bug-109410-4-kPnTnC6Avl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109410-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #12 from Sam James <sjames at gcc dot gnu.org> ---
Bisect gives a nonsensical result of r13-7156-g31eb8f18bbe646 with initial good
as r13-7155-g51856718a82ce60f067910d9037ca255645b37eb and bad as
releases/gcc-13.

I've checked out r13-7155-g51856718a82ce60f067910d9037ca255645b37eb and with
that commit, the test case still fails:
```
$ /tmp/bisect/bin/gcc -c -g -O1
/home/sam/git/gcc/gcc/testsuite/gcc.dg/pr109410.c
/home/sam/git/gcc/gcc/testsuite/gcc.dg/pr109410.c: In function ‘foo’:
/home/sam/git/gcc/gcc/testsuite/gcc.dg/pr109410.c:14:1: error: returns_twice
call is not first in basic block 2
   14 | foo (int x, int y)
      | ^~~
baz (x_7(D), y_8(D));
during GIMPLE pass: reassoc
/home/sam/git/gcc/gcc/testsuite/gcc.dg/pr109410.c:14:1: internal compiler
error: verify_flow_info failed
0x9c06ee verify_flow_info()
        ../.././gcc/cfghooks.cc:285
0xdb8077 execute_function_todo
        ../.././gcc/passes.cc:2110
0xdb85be execute_todo
        ../.././gcc/passes.cc:2152
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
```

with:
```
gcc (GCC) 13.0.1 20230412 (experimental)
Copyright (C) 2023 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
```

so I don't think the original fix is complete?

  parent reply	other threads:[~2023-04-23  3:58 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-04 16:10 [Bug c/109410] New: " gscfq@t-online.de
2023-04-04 20:50 ` [Bug tree-optimization/109410] " pinskia at gcc dot gnu.org
2023-04-04 20:53 ` pinskia at gcc dot gnu.org
2023-04-04 20:58 ` pinskia at gcc dot gnu.org
2023-04-11 12:31 ` rguenth at gcc dot gnu.org
2023-04-11 14:33 ` jakub at gcc dot gnu.org
2023-04-12  5:00 ` sjames at gcc dot gnu.org
2023-04-12 14:55 ` cvs-commit at gcc dot gnu.org
2023-04-12 14:58 ` jakub at gcc dot gnu.org
2023-04-18  7:16 ` cvs-commit at gcc dot gnu.org
2023-04-22 12:41 ` dcb314 at hotmail dot com
2023-04-22 12:58 ` sjames at gcc dot gnu.org
2023-04-23  2:45 ` sjames at gcc dot gnu.org
2023-04-23  3:58 ` sjames at gcc dot gnu.org [this message]
2023-04-23  4:07 ` pinskia at gcc dot gnu.org
2023-04-23  4:11 ` pinskia at gcc dot gnu.org
2023-04-26  6:58 ` [Bug tree-optimization/109410] [13/14 " rguenth at gcc dot gnu.org
2023-05-02 20:16 ` cvs-commit at gcc dot gnu.org
2023-05-03 15:23 ` cvs-commit at gcc dot gnu.org
2023-07-27  9:25 ` rguenth at gcc dot gnu.org
2024-05-21  9:14 ` [Bug tree-optimization/109410] [13/14/15 " 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-109410-4-kPnTnC6Avl@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).