public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/99702] [11 Regression] ICE: RTL check: expected code 'const_int', have 'subreg' in riscv_expand_block_move, at config/riscv/riscv.c:3262 with memcpy() Date: Sun, 21 Mar 2021 21:00:22 +0000 [thread overview] Message-ID: <bug-99702-4-IYB7phYw6T@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99702-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99702 Zdenek Sojka <zsojka at seznam dot cz> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to fail| |11.0 --- Comment #1 from Zdenek Sojka <zsojka at seznam dot cz> --- This might be a recent regression, r11-7696 works fine.
next prev parent reply other threads:[~2021-03-21 21:00 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-21 20:59 [Bug target/99702] New: " zsojka at seznam dot cz 2021-03-21 21:00 ` zsojka at seznam dot cz [this message] 2021-03-22 8:26 ` [Bug target/99702] [11 Regression] ICE: RTL check: expected code 'const_int', have 'subreg' in riscv_expand_block_move, at config/riscv/riscv.c:3262 with memcpy() since r11-7757-gfc9c4e5fc50c7fcbd27d6cb3dd372f7da8216954 marxin at gcc dot gnu.org 2021-03-22 8:32 ` zsojka at seznam dot cz 2021-03-22 8:39 ` kito at gcc dot gnu.org 2021-03-22 8:40 ` [Bug target/99702] [11 Regression] ICE: RTL check: expected code 'const_int', have 'subreg' in riscv_expand_block_move, at config/riscv/riscv.c:3262 with memcpy() since g:d9f0ade001533c9544bf2153b6baa8844ec0bee4 marxin at gcc dot gnu.org 2021-03-22 9:47 ` cvs-commit at gcc dot gnu.org 2021-03-22 9:49 ` kito at gcc dot gnu.org 2021-03-22 10:06 ` cvs-commit at gcc dot gnu.org 2021-03-22 10:07 ` cvs-commit 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-99702-4-IYB7phYw6T@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).