public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/95171] New: ICE: verify_flow_info failed (error: wrong outgoing edge flags at end of bb 2)
Date: Sun, 17 May 2020 04:55:01 +0000	[thread overview]
Message-ID: <bug-95171-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 95171
           Summary: ICE: verify_flow_info failed (error: wrong outgoing
                    edge flags at end of bb 2)
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: asolokha at gmx dot com
  Target Milestone: ---

gcc-11.0.0-alpha20200510 snapshot (g:13a46321516e2efd3bbb1f1899c539c6724240a9)
ICEs when compiling the following testcase w/ -fexceptions -ffinite-math-only
-fnon-call-exceptions (optionally, any optimization level except -Ofast can be
specified):

inline double __attribute__ ((always_inline))
w9 (int q2)
{
  return __builtin_fabs (__builtin_nan ("")) > 0.0 ? 1.0 : q2 / 1.0;
}

double __attribute__ ((optimize ("")))
o7 (int iz)
{
  int rj[1];

  (void) rj;

  return w9 (iz);
}

% gcc-11.0.0 -fexceptions -ffinite-math-only -fnon-call-exceptions -c
eqf0xkza.c
eqf0xkza.c:9:1: warning: bad option '-f' to attribute 'optimize' [-Wattributes]
    9 | {
      | ^
eqf0xkza.c: In function 'o7':
eqf0xkza.c:15:1: error: wrong outgoing edge flags at end of bb 2
   15 | }
      | ^
during GIMPLE pass: einline
eqf0xkza.c:15:1: internal compiler error: verify_flow_info failed
0x9059a7 verify_flow_info()
       
/var/tmp/portage/sys-devel/gcc-11.0.0_alpha20200510/work/gcc-11-20200510/gcc/cfghooks.c:269
0xde57d4 checking_verify_flow_info
       
/var/tmp/portage/sys-devel/gcc-11.0.0_alpha20200510/work/gcc-11-20200510/gcc/cfghooks.h:212
0xde57d4 cleanup_tree_cfg_noloop
       
/var/tmp/portage/sys-devel/gcc-11.0.0_alpha20200510/work/gcc-11-20200510/gcc/tree-cfgcleanup.c:1114
0xde5dd8 cleanup_tree_cfg(unsigned int)
       
/var/tmp/portage/sys-devel/gcc-11.0.0_alpha20200510/work/gcc-11-20200510/gcc/tree-cfgcleanup.c:1165
0xcb744c execute_function_todo
       
/var/tmp/portage/sys-devel/gcc-11.0.0_alpha20200510/work/gcc-11-20200510/gcc/passes.c:1951
0xcb81ac do_per_function
       
/var/tmp/portage/sys-devel/gcc-11.0.0_alpha20200510/work/gcc-11-20200510/gcc/passes.c:1640
0xcb81ac execute_todo
       
/var/tmp/portage/sys-devel/gcc-11.0.0_alpha20200510/work/gcc-11-20200510/gcc/passes.c:2039

             reply	other threads:[~2020-05-17  4:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-17  4:55 asolokha at gmx dot com [this message]
2020-05-18  5:52 ` [Bug tree-optimization/95171] " marxin at gcc dot gnu.org
2020-05-18  6:04 ` rguenth at gcc dot gnu.org
2020-05-18  6:26 ` rguenth at gcc dot gnu.org
2020-05-18 10:28 ` cvs-commit at gcc dot gnu.org
2020-05-18 10:28 ` rguenth at gcc dot gnu.org
2020-05-20 11:28 ` rguenth at gcc dot gnu.org
2020-12-01 15:44 ` cvs-commit at gcc dot gnu.org
2021-09-16  1:36 ` pinskia 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-95171-4@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).