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/102991] [12 regression] gcc.dg/vect/vect-simd-17.c fails after r12-4757 Date: Tue, 09 Nov 2021 01:27:11 +0000 [thread overview] Message-ID: <bug-102991-4-NyfUs9gYvN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102991-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102991 --- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Xiong Hu Luo <luoxhu@gcc.gnu.org>: https://gcc.gnu.org/g:0c877d1c30ef1c5145817805ab944cddea61ad54 commit r11-9231-g0c877d1c30ef1c5145817805ab944cddea61ad54 Author: Xionghu Luo <luoxhu@linux.ibm.com> Date: Wed Nov 3 20:23:03 2021 -0500 rs6000: Fix incorrect fusion constraint [PR102991] gcc/ChangeLog: 2021-11-05 Xionghu Luo <luoxhu@linux.ibm.com> PR target/102991 * config/rs6000/fusion.md: Regenerate. * config/rs6000/genfusion.pl: Fix incorrect clobber constraint. (cherry picked from commit 614b39757b8b61f70ac1c666edb7a01a5fc19cd4)
next prev parent reply other threads:[~2021-11-09 1:27 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-28 18:30 [Bug target/102991] New: [12 regress] " seurer at gcc dot gnu.org 2021-10-29 6:49 ` [Bug target/102991] [12 regression] " rguenth at gcc dot gnu.org 2021-10-29 9:11 ` luoxhu at gcc dot gnu.org 2021-10-29 9:55 ` linkw at gcc dot gnu.org 2021-11-01 5:03 ` luoxhu at gcc dot gnu.org 2021-11-02 8:18 ` luoxhu at gcc dot gnu.org 2021-11-02 8:36 ` luoxhu at gcc dot gnu.org 2021-11-05 5:39 ` cvs-commit at gcc dot gnu.org 2021-11-05 5:44 ` luoxhu at gcc dot gnu.org 2021-11-09 1:27 ` cvs-commit at gcc dot gnu.org [this message] 2021-11-09 1:28 ` luoxhu 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-102991-4-NyfUs9gYvN@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).