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/105165] New: [11/12 Regression] ICE in gimple_redirect_edge_and_branch, at tree-cfg.cc:6136
Date: Tue, 05 Apr 2022 16:18:25 +0000	[thread overview]
Message-ID: <bug-105165-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 105165
           Summary: [11/12 Regression] ICE in
                    gimple_redirect_edge_and_branch, at tree-cfg.cc:6136
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gscfq@t-online.de
  Target Milestone: ---

Started between 20201108 and 20201115, at -O1+ :
(derived from pr100329.c)


$ cat z1.c
unsigned int _Complex a0;
unsigned int _Complex
foo (unsigned int _Complex a1, unsigned int _Complex a2)
{
  unsigned int _Complex x;
  asm goto ("" : "=r" (x) : : : lab);
  a0 = x;
 lab:
  return x + a1 + a2 + 1;
}


$ gcc-12-20220403 -c z1.c -O2
during GIMPLE pass: pre
z1.c: In function 'foo':
z1.c:3:1: internal compiler error: in gimple_redirect_edge_and_branch, at
tree-cfg.cc:6136
    3 | foo (unsigned int _Complex a1, unsigned int _Complex a2)
      | ^~~
0xc611c5 gimple_redirect_edge_and_branch
        ../../gcc/tree-cfg.cc:6136
0x7d3139 redirect_edge_and_branch(edge_def*, basic_block_def*)
        ../../gcc/cfghooks.cc:388
0xc593b8 gimple_split_edge
        ../../gcc/tree-cfg.cc:2983
0x7d37c5 split_edge(edge_def*)
        ../../gcc/cfghooks.cc:668
0xc61f67 split_critical_edges(bool)
        ../../gcc/tree-cfg.cc:9172
0xda6ab1 split_edges_for_insertion()
        ../../gcc/tree-cfg.h:130
0xda6ab1 execute
        ../../gcc/tree-ssa-pre.cc:4402

             reply	other threads:[~2022-04-05 16:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-05 16:18 gscfq@t-online.de [this message]
2022-04-05 16:30 ` [Bug c/105165] " jakub at gcc dot gnu.org
2022-04-06  7:53 ` [Bug tree-optimization/105165] " rguenth at gcc dot gnu.org
2022-04-06 10:43 ` rguenth at gcc dot gnu.org
2022-04-06 11:10 ` jakub at gcc dot gnu.org
2022-04-06 11:22 ` rguenther at suse dot de
2022-04-06 11:31 ` jakub at gcc dot gnu.org
2022-04-06 11:36 ` rguenth at gcc dot gnu.org
2022-04-07  6:17 ` [Bug tree-optimization/105165] Complex lowering does not handle asm goto with complex output; " cvs-commit at gcc dot gnu.org
2022-04-07  7:00 ` cvs-commit at gcc dot gnu.org
2022-04-07  7:01 ` rguenth 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-105165-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).