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/96762] ICE in extract_insn, at recog.c:2294 (error: unrecognizable insn) Date: Tue, 12 Sep 2023 01:58:51 +0000 [thread overview] Message-ID: <bug-96762-4-IP9LX8XklC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96762-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96762 --- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by HaoChen Gui <guihaoc@gcc.gnu.org>: https://gcc.gnu.org/g:2eb8e5cba7408e2a4016a8f5c48e4980abdd1d08 commit r11-10985-g2eb8e5cba7408e2a4016a8f5c48e4980abdd1d08 Author: Haochen Gui <guihaoc@gcc.gnu.org> Date: Tue Sep 12 09:58:08 2023 +0800 rs6000: call vector load/store with length only on 64-bit Power10 gcc/ PR target/96762 * config/rs6000/rs6000-string.c (expand_block_move): Call vector load/store with length only on 64-bit Power10. gcc/testsuite/ PR target/96762 * gcc.target/powerpc/pr96762.c: New. (cherry picked from commit 946b8967b905257ac9f140225db744c9a6ab91be)
next prev parent reply other threads:[~2023-09-12 1:58 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-24 9:33 [Bug target/96762] New: " asolokha at gmx dot com 2021-05-27 20:26 ` [Bug target/96762] " meissner at gcc dot gnu.org 2021-05-29 18:23 ` meissner at gcc dot gnu.org 2021-05-29 19:53 ` segher at gcc dot gnu.org 2023-06-02 3:02 ` bergner at gcc dot gnu.org 2023-08-30 2:31 ` linkw at gcc dot gnu.org 2023-08-31 5:44 ` cvs-commit at gcc dot gnu.org 2023-09-12 1:54 ` cvs-commit at gcc dot gnu.org 2023-09-12 1:56 ` cvs-commit at gcc dot gnu.org 2023-09-12 1:58 ` cvs-commit at gcc dot gnu.org [this message] 2023-09-12 1:59 ` guihaoc 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-96762-4-IP9LX8XklC@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).