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/109932] ICE in in extract_insn, at recog.cc:2791 on ppc64le with -mno-vsx Date: Tue, 20 Jun 2023 03:21:40 +0000 [thread overview] Message-ID: <bug-109932-4-GUtnqYwGU4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109932-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109932 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-13 branch has been updated by Kewen Lin <linkw@gcc.gnu.org>: https://gcc.gnu.org/g:4b4a21c93406aef276fbff00d3e9491285d7b4a9 commit r13-7458-g4b4a21c93406aef276fbff00d3e9491285d7b4a9 Author: Kewen Lin <linkw@linux.ibm.com> Date: Tue Jun 13 03:04:54 2023 -0500 testsuite: Check int128 effective target for pr109932-{1,2}.c [PR110230] This patch is to make newly added test cases pr109932-{1,2}.c check int128 effective target to avoid unsupported type error on 32-bit. I did hit this failure during testing and fixed it, but made a stupid mistake not updating the local formatted patch which was actually out of date. PR testsuite/110230 PR target/109932 gcc/testsuite/ChangeLog: * gcc.target/powerpc/pr109932-1.c: Adjust with int128 effective target. * gcc.target/powerpc/pr109932-2.c: Ditto. (cherry picked from commit 16eb9d69079d769b2aa2c07ce54aca20f5547c14)
next prev parent reply other threads:[~2023-06-20 3:21 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-22 17:05 [Bug target/109932] New: " jamborm at gcc dot gnu.org 2023-05-24 2:23 ` [Bug target/109932] " linkw at gcc dot gnu.org 2023-06-12 6:10 ` cvs-commit at gcc dot gnu.org 2023-06-13 8:08 ` cvs-commit at gcc dot gnu.org 2023-06-20 3:20 ` cvs-commit at gcc dot gnu.org 2023-06-20 3:20 ` cvs-commit at gcc dot gnu.org 2023-06-20 3:21 ` cvs-commit at gcc dot gnu.org 2023-06-20 3:21 ` cvs-commit at gcc dot gnu.org [this message] 2023-06-20 8:24 ` cvs-commit at gcc dot gnu.org 2023-06-20 9:30 ` cvs-commit at gcc dot gnu.org 2023-06-20 9:42 ` linkw 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-109932-4-GUtnqYwGU4@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).