public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/102133] New: [12 Regression] ICE in set_rtl building libgcc __muldc3 for 32-bit SPARC Date: Mon, 30 Aug 2021 19:03:05 +0000 [thread overview] Message-ID: <bug-102133-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102133 Bug ID: 102133 Summary: [12 Regression] ICE in set_rtl building libgcc __muldc3 for 32-bit SPARC Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: jsm28 at gcc dot gnu.org CC: liuhongt at gcc dot gnu.org Target Milestone: --- Target: sparc*-*-* Created attachment 51380 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51380&action=edit preprocessed source commit 7218c2ec365ce95f5a1012a6eb425b0a36aec6bf, "Make sure we're playing with integral modes before call extract_integral_bit_field.", introduces the following ICE building libgcc for 32-bit SPARC (32-bit multilib for sparc64-linux-gnu). Compile the attached test with -m32 -O2. during RTL pass: expand /scratch/jmyers/glibc/many12/src/gcc/libgcc/libgcc2.c: In function '__muldc3': /scratch/jmyers/glibc/many12/src/gcc/libgcc/libgcc2.c:1947:1: internal compiler error: in set_rtl, at cfgexpand.c:200 1947 | CONCAT3(__mul,MODE,3) (MTYPE a, MTYPE b, MTYPE c, MTYPE d) | ^~~~~~~~ 0x7ccbe9 set_rtl /scratch/jmyers/glibc/many12/src/gcc/gcc/cfgexpand.c:179 0x7cf028 set_parm_rtl(tree_node*, rtx_def*) /scratch/jmyers/glibc/many12/src/gcc/gcc/cfgexpand.c:1401 0x98a451 assign_parm_setup_reg /scratch/jmyers/glibc/many12/src/gcc/gcc/function.c:3401 0x98a451 assign_parms /scratch/jmyers/glibc/many12/src/gcc/gcc/function.c:3707 0x98de2c expand_function_start(tree_node*) /scratch/jmyers/glibc/many12/src/gcc/gcc/function.c:5163 0x7e11b9 execute /scratch/jmyers/glibc/many12/src/gcc/gcc/cfgexpand.c:6692 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions.
next reply other threads:[~2021-08-30 19:03 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-30 19:03 jsm28 at gcc dot gnu.org [this message] 2021-08-30 19:09 ` [Bug middle-end/102133] " pinskia at gcc dot gnu.org 2021-08-31 1:20 ` crazylht at gmail dot com 2021-08-31 1:51 ` crazylht at gmail dot com 2021-08-31 2:04 ` crazylht at gmail dot com 2021-08-31 2:16 ` crazylht at gmail dot com 2021-08-31 2:49 ` crazylht at gmail dot com 2021-08-31 3:01 ` crazylht at gmail dot com 2021-08-31 3:29 ` crazylht at gmail dot com 2021-08-31 4:59 ` crazylht at gmail dot com 2021-08-31 7:23 ` rguenth at gcc dot gnu.org 2021-08-31 10:09 ` mikpelinux at gmail dot com 2021-09-01 1:08 ` cvs-commit at gcc dot gnu.org 2021-09-01 1:24 ` crazylht at gmail dot com 2022-01-17 13:52 ` 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-102133-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: linkBe 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).