public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/109179] [13 Regression] addkf3-sw.c:51:1: internal compiler error: RTL check: expected elt 3 type 'e' or 'u', have '0' Date: Fri, 17 Mar 2023 20:46:49 +0000 [thread overview] Message-ID: <bug-109179-4-mkBCaJosYs@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109179-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109179 --- Comment #8 from Peter Bergner <bergner at gcc dot gnu.org> --- Here's another creduced test case, this one with -O2 optimization: bergner@ltcden2-lp1:PR109179$ cat bug2.i union u { _Float128 flt; long sign; }; _Float128 foo (long src) { union u var; var.sign = src; return var.flt; } bergner@ltcden2-lp1:PR109179$ gcc -S -O2 -mcpu=power8 bug2.i during RTL pass: reload bug2.i: In function ‘foo’: bug2.i:13:1: internal compiler error: RTL check: expected elt 3 type 'e' or 'u', have '0' (rtx note) in PATTERN, at rtl.h:1509 13 | } | ^ 0x1148c663 rtl_check_failed_type2(rtx_def const*, int, int, int, char const*, int, char const*) /home/bergner/gcc/gcc-fsf-mainline-chip-ice/gcc/rtl.cc:907 0x10a0a207 PATTERN(rtx_def*) /home/bergner/gcc/gcc-fsf-mainline-chip-ice/gcc/rtl.h:1509 0x1278c123 insn_extract(rtx_insn*) /home/bergner/gcc/build/gcc-fsf-mainline-chip-ice-regtest/gcc/insn-extract.cc:23 0x1118c9e7 lra_set_insn_recog_data(rtx_insn*) /home/bergner/gcc/gcc-fsf-mainline-chip-ice/gcc/lra.cc:1059 0x11194f23 lra_get_insn_recog_data(rtx_insn*) /home/bergner/gcc/gcc-fsf-mainline-chip-ice/gcc/lra-int.h:493 0x111b8de7 combine_reload_insn /home/bergner/gcc/gcc-fsf-mainline-chip-ice/gcc/lra-constraints.cc:5017
next prev parent reply other threads:[~2023-03-17 20:46 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-17 19:38 [Bug target/109179] New: " bergner at gcc dot gnu.org 2023-03-17 19:39 ` [Bug target/109179] " bergner at gcc dot gnu.org 2023-03-17 19:43 ` bergner at gcc dot gnu.org 2023-03-17 20:05 ` bergner at gcc dot gnu.org 2023-03-17 20:12 ` bergner at gcc dot gnu.org 2023-03-17 20:14 ` bergner at gcc dot gnu.org 2023-03-17 20:18 ` [Bug rtl-optimization/109179] " bergner at gcc dot gnu.org 2023-03-17 20:29 ` vmakarov at gcc dot gnu.org 2023-03-17 20:29 ` [Bug rtl-optimization/109179] [13 Regression] " pinskia at gcc dot gnu.org 2023-03-17 20:38 ` jakub at gcc dot gnu.org 2023-03-17 20:46 ` bergner at gcc dot gnu.org [this message] 2023-03-17 20:48 ` vmakarov at gcc dot gnu.org 2023-03-17 20:50 ` bergner at gcc dot gnu.org 2023-03-17 20:51 ` jakub at gcc dot gnu.org 2023-03-17 21:04 ` bergner at gcc dot gnu.org 2023-03-17 21:09 ` bergner at gcc dot gnu.org 2023-03-17 21:13 ` vmakarov at gcc dot gnu.org 2023-03-17 21:23 ` bergner at gcc dot gnu.org 2023-03-17 21:27 ` jakub at gcc dot gnu.org 2023-03-17 21:34 ` bergner at gcc dot gnu.org 2023-03-17 21:54 ` bergner at gcc dot gnu.org 2023-03-17 22:03 ` bergner at gcc dot gnu.org 2023-03-17 22:06 ` jakub at gcc dot gnu.org 2023-03-17 22:13 ` vmakarov at gcc dot gnu.org 2023-03-18 0:03 ` cvs-commit at gcc dot gnu.org 2023-03-18 0:05 ` bergner 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-109179-4-mkBCaJosYs@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).