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/100418] [12 Regression][gcn] since r12-397 bootstrap fails: error: unrecognizable insn: in extract_insn, at recog.c:2770 Date: Wed, 05 May 2021 10:36:16 +0000 [thread overview] Message-ID: <bug-100418-4-DRZ3Xx9JdD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100418-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100418 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> --- LRA uses for this kind of things emit_add2_insn. This is during expansion though, and I think other spots e.g. in builtins.c use in such cases builtins.c- ret = plus_constant (GET_MODE (ret), ret, INTVAL (len_rtx)); builtins.c: ret = emit_move_insn (target, force_operand (ret, NULL_RTX)); instead, so I'd certainly try: --- gcc/builtins.c.jj 2021-05-04 21:02:23.954802278 +0200 +++ gcc/builtins.c 2021-05-05 12:35:51.990008546 +0200 @@ -6775,7 +6775,8 @@ try_store_by_multiple_pieces (rtx to, rt PTR+offset, we have to replace it. */ emit_move_insn (ptr, XEXP (to, 0)); to = replace_equiv_address (to, ptr); - emit_move_insn (rem, plus_constant (ptr_mode, rem, -blksize)); + rtx rem_minus_blksize = plus_constant (ptr_mode, rem, -blksize); + emit_move_insn (rem, force_operand (rem_minus_blksize, NULL_RTX)); } /* Iterate over power-of-two block sizes from the maximum length to @@ -6811,7 +6812,8 @@ try_store_by_multiple_pieces (rtx to, rt { emit_move_insn (ptr, XEXP (to, 0)); to = replace_equiv_address (to, ptr); - emit_move_insn (rem, plus_constant (ptr_mode, rem, -blksize)); + rtx rem_minus_blksize = plus_constant (ptr_mode, rem, -blksize); + emit_move_insn (rem, force_operand (rem_minus_blksize, NULL_RTX)); } if (label)
next prev parent reply other threads:[~2021-05-05 10:36 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-04 14:57 [Bug target/100418] New: " burnus at gcc dot gnu.org 2021-05-04 16:52 ` [Bug target/100418] " burnus at gcc dot gnu.org 2021-05-04 21:51 ` burnus at gcc dot gnu.org 2021-05-05 6:28 ` rguenth at gcc dot gnu.org 2021-05-05 10:24 ` ams at gcc dot gnu.org 2021-05-05 10:36 ` jakub at gcc dot gnu.org [this message] 2021-05-05 11:24 ` ams at gcc dot gnu.org 2021-05-05 11:49 ` burnus at gcc dot gnu.org 2021-05-05 12:16 ` jakub at gcc dot gnu.org 2021-05-05 13:41 ` ams at gcc dot gnu.org 2021-05-06 6:57 ` dcb314 at hotmail dot com 2021-05-06 7:29 ` burnus at gcc dot gnu.org 2021-05-06 10:28 ` dcb314 at hotmail dot com 2021-05-06 10:38 ` ams at gcc dot gnu.org 2021-05-06 11:02 ` jakub at gcc dot gnu.org 2021-05-06 11:05 ` dcb314 at hotmail dot com 2021-05-07 22:48 ` cvs-commit at gcc dot gnu.org 2021-05-14 11:07 ` ams 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-100418-4-DRZ3Xx9JdD@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).