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/102146] [11 regression] several test cases fails after r11-8940 Date: Tue, 16 Aug 2022 21:24:16 +0000 [thread overview] Message-ID: <bug-102146-4-DinHJnraMj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102146-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102146 --- Comment #17 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Segher Boessenkool <segher@gcc.gnu.org>: https://gcc.gnu.org/g:72cf56c7cfefaf1b074bb70e42890cf1191c46a1 commit r11-10208-g72cf56c7cfefaf1b074bb70e42890cf1191c46a1 Author: Segher Boessenkool <segher@kernel.crashing.org> Date: Thu Apr 21 18:35:32 2022 +0000 rs6000/testsuite: xfail bswap-brw.c This testcase does not generate anywhere near optimal code for 32-bit code. For p10 it actually now fails this testcase, after the previous patch. Let's xfail it. 2022-04-21 Segher Boessenkool <segher@kernel.crashing.org> gcc/testsuite/ PR target/103197 PR target/102146 * gcc.target/powerpc/bswap-brw.c: Add xfail on scan-assembler for -m32. (cherry picked from commit 748d46cd049c89a799f99f14547267ebae915af6)
next prev parent reply other threads:[~2022-08-16 21:24 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-31 15:11 [Bug target/102146] New: " seurer at gcc dot gnu.org 2021-09-01 8:23 ` [Bug target/102146] " rguenth at gcc dot gnu.org 2021-09-02 8:24 ` guihaoc at gcc dot gnu.org 2022-04-07 8:34 ` rguenth at gcc dot gnu.org 2022-04-07 8:50 ` jakub at gcc dot gnu.org 2022-04-08 1:19 ` guihaoc at gcc dot gnu.org 2022-04-08 1:26 ` guihaoc at gcc dot gnu.org 2022-04-12 0:46 ` aoliva at gcc dot gnu.org 2022-04-13 1:43 ` cvs-commit at gcc dot gnu.org 2022-04-13 7:25 ` rguenth at gcc dot gnu.org 2022-04-14 0:41 ` guihaoc at gcc dot gnu.org 2022-04-14 1:11 ` guihaoc at gcc dot gnu.org 2022-04-21 21:31 ` cvs-commit at gcc dot gnu.org 2022-04-21 21:31 ` cvs-commit at gcc dot gnu.org 2022-05-19 22:13 ` bergner at gcc dot gnu.org 2022-05-19 23:06 ` bergner at gcc dot gnu.org 2022-05-20 0:54 ` guihaoc at gcc dot gnu.org 2022-08-16 21:24 ` cvs-commit at gcc dot gnu.org 2022-08-16 21:24 ` cvs-commit at gcc dot gnu.org [this message] 2022-08-16 23:35 ` cvs-commit at gcc dot gnu.org 2022-08-16 23:40 ` segher at gcc dot gnu.org 2022-08-17 2:20 ` guihaoc at gcc dot gnu.org 2022-08-24 16:58 ` segher at gcc dot gnu.org 2023-04-03 3:15 ` cvs-commit at gcc dot gnu.org 2023-04-18 1:59 ` 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-102146-4-DinHJnraMj@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).