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/105334] ICE in curr_insn_transform, at lra-constraints.cc:4168 (error: unable to generate reloads) Date: Thu, 28 Apr 2022 03:35:41 +0000 [thread overview] Message-ID: <bug-105334-4-zbKHmvNqjK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105334-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105334 --- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Kewen Lin <linkw@gcc.gnu.org>: https://gcc.gnu.org/g:84c1c9b013faf8cdac31db3f6612bd9d5f70ddb3 commit r12-8296-g84c1c9b013faf8cdac31db3f6612bd9d5f70ddb3 Author: Kewen Lin <linkw@linux.ibm.com> Date: Wed Apr 27 22:34:27 2022 -0500 testsuite: Add test case for pack/unpack bifs at soft-float [PR105334] This patch is to add the test coverage for the two recent fixes r12-8091 and r12-8226 from Segher, aix is skipped since it takes soft-float and long-double-128 incompatible. PR target/105334 gcc/testsuite/ChangeLog: * gcc.target/powerpc/pr105334.c: New test.
next prev parent reply other threads:[~2022-04-28 3:35 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-21 13:07 [Bug target/105334] New: [12 Regression] " asolokha at gmx dot com 2022-04-21 18:02 ` [Bug target/105334] " segher at gcc dot gnu.org 2022-04-21 18:05 ` segher at gcc dot gnu.org 2022-04-21 22:54 ` segher at gcc dot gnu.org 2022-04-21 23:50 ` segher at gcc dot gnu.org 2022-04-22 2:33 ` linkw at gcc dot gnu.org 2022-04-22 5:58 ` rguenth at gcc dot gnu.org 2022-04-22 19:29 ` cvs-commit at gcc dot gnu.org 2022-04-22 19:54 ` segher at gcc dot gnu.org 2022-04-26 8:46 ` [Bug target/105334] " jakub at gcc dot gnu.org 2022-04-28 3:35 ` cvs-commit at gcc dot gnu.org [this message] 2022-04-28 3:39 ` 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-105334-4-zbKHmvNqjK@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).