public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/102752] New: [12 Regression] Recent change to ldist causing ICE on msp430-elf, rl78-elf, and xstormy16-elf
Date: Thu, 14 Oct 2021 17:11:42 +0000	[thread overview]
Message-ID: <bug-102752-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 102752
           Summary: [12 Regression] Recent change to ldist causing ICE on
                    msp430-elf, rl78-elf, and xstormy16-elf
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: law at gcc dot gnu.org
  Target Milestone: ---

After this change:


msp430-elf, rl78-elf and xstormy16-elf are all getting an ICE on
gcc.c-torture/execute/

>From the msp430-elf gcc.log file:

/home/jlaw/jenkins/workspace/msp430-elf/gcc/gcc/testsuite/gcc.c-torture/execute/20100827-1.c:
In function 'foo':^M
/home/jlaw/jenkins/workspace/msp430-elf/gcc/gcc/testsuite/gcc.c-torture/execute/20100827-1.c:3:1:
internal compiler error: tree check: expected class 'type', have 'exceptional'
(ssa_name) in transform_reduction_loop, at tree-loop-distribution.c:3684^M
0x1532ceb tree_class_check_failed(tree_node const*, tree_code_class, char
const*, int, char const*)^M
        ../../..//gcc/gcc/tree.c:8739^M
0x861c29 tree_class_check(tree_node*, tree_code_class, char const*, int, char
const*)^M
        ../../..//gcc/gcc/tree.h:3556^M
0x12006d9 loop_distribution::transform_reduction_loop(loop*)^M
        ../../..//gcc/gcc/tree-loop-distribution.c:3684^M
0x1200d92 loop_distribution::execute(function*)^M
        ../../..//gcc/gcc/tree-loop-distribution.c:3776^M
0x12012bd execute^M
        ../../..//gcc/gcc/tree-loop-distribution.c:3901^M
Please submit a full bug report,^M

You should be able to reproduce this with just a cross compiler.  No assembler
or target libraries should be needed.

             reply	other threads:[~2021-10-14 17:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-14 17:11 law at gcc dot gnu.org [this message]
2021-10-14 17:14 ` [Bug tree-optimization/102752] " law at gcc dot gnu.org
2021-10-14 18:07 ` stefansf at linux dot ibm.com
2021-10-14 18:11 ` law at gcc dot gnu.org
2021-10-14 23:41 ` law at gcc dot gnu.org
2021-10-15  6:18 ` rguenth at gcc dot gnu.org
2021-10-15  9:41 ` stefansf at linux dot ibm.com
2021-10-15  9:43 ` stefansf at linux dot ibm.com
2021-10-15 14:41 ` law 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-102752-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).