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/95683] RISC-V: internal compiler error: in riscv_gpr_save_operation_p, at config/riscv/riscv.c:5219 Date: Thu, 09 Jul 2020 07:25:20 +0000 [thread overview] Message-ID: <bug-95683-4-3p5vKqB95N@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95683-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95683 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Kito Cheng <kito@gcc.gnu.org>: https://gcc.gnu.org/g:01b774ff3adcae0e72548f050795c1cf6bf5b8fe commit r10-8445-g01b774ff3adcae0e72548f050795c1cf6bf5b8fe Author: Kito Cheng <kito.cheng@sifive.com> Date: Tue Jun 16 10:14:13 2020 +0800 RISC-V: Fix ICE on riscv_gpr_save_operation_p [PR95683] - riscv_gpr_save_operation_p might try to match parallel on other patterns like inline asm pattern, and then it might trigger ther assertion checking there, so we could trun it into a early exit check. gcc/ChangeLog: PR target/95683 * config/riscv/riscv.c (riscv_gpr_save_operation_p): Remove assertion and turn it into a early exit check. gcc/testsuite/ChangeLog PR target/95683 * gcc.target/riscv/pr95683.c: New. (cherry picked from commit beaf12b49ae030505194cdcac18b5c8533a43921)
prev parent reply other threads:[~2020-07-09 7:25 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-15 14:23 [Bug target/95683] New: " kito.cheng at gmail dot com 2020-06-15 14:27 ` [Bug target/95683] RISC-V: " kito at gcc dot gnu.org 2020-06-16 2:15 ` cvs-commit at gcc dot gnu.org 2020-06-19 5:49 ` kito at gcc dot gnu.org 2020-07-09 7:25 ` cvs-commit at gcc dot gnu.org [this message]
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-95683-4-3p5vKqB95N@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).