public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/105247] [11/12 Regression] IA64: ICE on sqlite-3.38.2: in decompose, at rtl.h:2288 since r11-5271-g4866b2f5db117f Date: Wed, 13 Apr 2022 11:11:58 +0000 [thread overview] Message-ID: <bug-105247-4-7EwjYIkc1E@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105247-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105247 --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> --- The problem is that the ia64 backend for some strange reason uses DImode for the shift last operands, while e.g. in GIMPLE they are converted to integer_type_node or so: /* Why oh why didn't Intel arrange for SHIFT_COUNT_TRUNCATED? Now we've got to get rid of stray bits outside the SImode register. */ rtx subshift = gen_reg_rtx (DImode); emit_insn (gen_zero_extendsidi2 (subshift, operands[2])); operands[2] = subshift; and simplify-rtx.cc simply uses the mode of the shift for the shift count.
next prev parent reply other threads:[~2022-04-13 11:11 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-12 17:42 [Bug target/105247] New: IA64: ICE on sqlite-3.38.2: in decompose, at rtl.h:2288 slyfox at gcc dot gnu.org 2022-04-13 5:26 ` [Bug target/105247] [11/12 Regression] IA64: ICE on sqlite-3.38.2: in decompose, at rtl.h:2288 since r11-5271-g4866b2f5db117f marxin at gcc dot gnu.org 2022-04-13 5:26 ` marxin at gcc dot gnu.org 2022-04-13 6:37 ` rguenth at gcc dot gnu.org 2022-04-13 11:11 ` jakub at gcc dot gnu.org [this message] 2022-04-13 11:17 ` jakub at gcc dot gnu.org 2022-04-14 11:48 ` cvs-commit at gcc dot gnu.org 2022-04-14 12:02 ` [Bug target/105247] [11 " jakub at gcc dot gnu.org 2022-04-21 7:51 ` rguenth at gcc dot gnu.org 2023-05-29 10:06 ` jakub 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-105247-4-7EwjYIkc1E@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).