public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/107305] New: ICE: 'verify_gimple' failed
Date: Tue, 18 Oct 2022 17:41:08 +0000	[thread overview]
Message-ID: <bug-107305-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 107305
           Summary: ICE: 'verify_gimple' failed
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gscfq@t-online.de
  Target Milestone: ---

Started with r7 :


$ cat z1.c
unsigned a;
static double *d;
static _Bool b;
__GIMPLE int
foo (int n)
{
  b = __builtin_add_overflow (n, *d, &a);
}


$ gcc-13-20221016 -c z1.c -fgimple
z1.c: In function 'foo':
z1.c:5:1: error: invalid argument to gimple call
    5 | foo (int n)
      | ^~~
*d
b = __builtin_add_overflow (n, *d, &a);
during GIMPLE pass: *warn_unused_result
z1.c:5:1: internal compiler error: 'verify_gimple' failed
0xf2c76d verify_gimple_in_seq(gimple*)
        ../../gcc/tree-cfg.cc:5301
0xdce2ca execute_function_todo
        ../../gcc/passes.cc:2093
0xdcebf2 execute_todo
        ../../gcc/passes.cc:2145

             reply	other threads:[~2022-10-18 17:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18 17:41 gscfq@t-online.de [this message]
2022-10-18 17:43 ` [Bug c/107305] " mpolacek at gcc dot gnu.org
2022-10-18 17:44 ` pinskia at gcc dot gnu.org
2022-10-19  6:47 ` marxin at gcc dot gnu.org
2022-10-19  7:16 ` rguenth at gcc dot gnu.org
2022-10-20  9:29 ` cvs-commit at gcc dot gnu.org
2022-10-20  9:31 ` rguenth at gcc dot gnu.org
2022-11-28 22:21 ` 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-107305-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).