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/106682] Powerpc test gcc.target/powerpc/pr86731-fwrapv-longlong.c fails on power8, passes on power9/power10 Date: Thu, 01 Sep 2022 05:28:04 +0000 [thread overview] Message-ID: <bug-106682-4-cHpQNiPDN2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106682-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106682 --- Comment #2 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:023c5b36e476976cb3b45ff32c7c64990c5a6d45 commit r13-2332-g023c5b36e476976cb3b45ff32c7c64990c5a6d45 Author: Kewen Lin <linkw@linux.ibm.com> Date: Thu Sep 1 00:27:11 2022 -0500 rs6000/test: Fix typo in pr86731-fwrapv-longlong.c [PR106682] Commit r12-2266 updated the scanned assembly content from "{\mlvx\M|\mlxv\M|\mlxvd2x\M}" to "{\mp?lxv\M|\mlxv\M|\mlxvd2x\M}" for the test case pr86731-fwrapv-longlong.c unexpectedly. It's meant to update "lxv" to "p?lxv", should leave the "lvx" unchanged. So fix the typo accordingly. PR testsuite/106682 gcc/testsuite/ChangeLog: * gcc.target/powerpc/pr86731-fwrapv-longlong.c: Fix typo.
next prev parent reply other threads:[~2022-09-01 5:28 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-106682-4@http.gcc.gnu.org/bugzilla/> 2022-08-29 8:18 ` linkw at gcc dot gnu.org 2022-09-01 5:28 ` cvs-commit at gcc dot gnu.org [this message] 2022-09-01 9:07 ` [Bug testsuite/106682] " linkw at gcc dot gnu.org 2024-01-04 7:37 ` linkw at gcc dot gnu.org 2024-01-20 17:21 ` pinskia 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-106682-4-cHpQNiPDN2@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).