public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/106586] riscv32 still broke with zba_zbb_zbc_zbs, ICE in do_SUBST in C++ code Date: Mon, 15 Aug 2022 21:37:29 +0000 [thread overview] Message-ID: <bug-106586-4-0vm7BW5Za3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106586-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106586 --- Comment #10 from Andrew Pinski <pinskia at gcc dot gnu.org> --- There is still some missing sign extend of the const_int. (insn 17 16 18 4 (set (reg:SI 77) (mem/u/c:SI (lo_sum:SI (reg/f:SI 78) (symbol_ref/u:SI ("*.LC0") [flags 0x82])) [0 S4 A32])) "t89.c":5:16 140 {*movsi_internal} (expr_list:REG_DEAD (reg/f:SI 78) (expr_list:REG_EQUAL (const_int 2147483648 [0x80000000]) (nil)))) Notice the REG_EQUAL. I think the issue is inside riscv_build_integer_1. Specifically this: alt_cost = 1 + riscv_build_integer_1 (alt_codes, value - low_part, mode);
next prev parent reply other threads:[~2022-08-15 21:37 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-11 17:40 [Bug target/106586] New: " pinskia at gcc dot gnu.org 2022-08-11 17:42 ` [Bug target/106586] " pinskia at gcc dot gnu.org 2022-08-11 17:46 ` pinskia at gcc dot gnu.org 2022-08-11 18:37 ` pinskia at gcc dot gnu.org 2022-08-11 18:47 ` pinskia at gcc dot gnu.org 2022-08-11 19:14 ` pinskia at gcc dot gnu.org 2022-08-11 22:16 ` pinskia at gcc dot gnu.org 2022-08-12 1:48 ` jiawei at iscas dot ac.cn 2022-08-12 1:55 ` pinskia at gcc dot gnu.org 2022-08-15 18:58 ` pinskia at gcc dot gnu.org 2022-08-15 21:37 ` pinskia at gcc dot gnu.org [this message] 2022-08-15 22:13 ` pinskia at gcc dot gnu.org 2022-08-15 22:20 ` pinskia at gcc dot gnu.org 2022-08-15 23:16 ` pinskia at gcc dot gnu.org 2022-08-24 19:20 ` cvs-commit at gcc dot gnu.org 2022-08-24 19:21 ` pinskia 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-106586-4-0vm7BW5Za3@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).