public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit 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: Fri, 07 May 2021 22:48:24 +0000 [thread overview] Message-ID: <bug-100418-4-F1UShxsIS6@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 --- Comment #16 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Andrew Stubbs <ams@gcc.gnu.org>: https://gcc.gnu.org/g:07d7d37d1a33efb04f1262e56f4b82d6e1089e75 commit r12-632-g07d7d37d1a33efb04f1262e56f4b82d6e1089e75 Author: Andrew Stubbs <ams@codesourcery.com> Date: Fri May 7 15:31:05 2021 +0100 Ensure emit_move_insn operands are valid Some architectures are fine with PLUS in move instructions, but others are not (amdgcn is the motivating example). 2021-05-07 Jakub Jelinek <jakub@redhat.com> Andrew Stubbs <amd@codesourcery.com> gcc/ChangeLog: PR target/100418 * builtins.c (try_store_by_multiple_pieces): Use force_operand for emit_move_insn operands.
next prev parent reply other threads:[~2021-05-07 22:48 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 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 [this message] 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-F1UShxsIS6@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).