public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/105349] [12 regression] gcc.target/powerpc/bswap-brw.c fails after r12-8221 Date: Sat, 23 Apr 2022 18:14:28 +0000 [thread overview] Message-ID: <bug-105349-4-YGe2z0NQ7N@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105349-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105349 --- Comment #1 from Segher Boessenkool <segher at gcc dot gnu.org> --- I actually had tested that: $ make check-gcc-c RUNTESTFLAGS="--target_board=unix'{-m64,-m32,-m32/-mpowerpc64}{-mcpu=power7,-mcpu=power8,-mcpu=power9,-mcpu=power10}' powerpc.exp=bswap-br*" === gcc Summary === # of expected passes 17 # of expected failures 1 # of unsupported tests 29 This is on powerpc64-linux. So what is different on your build, and what is that output change?
next prev parent reply other threads:[~2022-04-23 18:14 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-22 17:53 [Bug testsuite/105349] New: " seurer at gcc dot gnu.org 2022-04-23 18:14 ` segher at gcc dot gnu.org [this message] 2022-04-24 14:35 ` [Bug testsuite/105349] " segher at gcc dot gnu.org 2022-04-25 6:46 ` rguenth at gcc dot gnu.org 2022-04-25 16:06 ` jakub at gcc dot gnu.org 2022-04-25 16:36 ` jakub at gcc dot gnu.org 2022-04-25 16:49 ` segher at gcc dot gnu.org 2022-04-25 17:23 ` jakub at gcc dot gnu.org 2022-04-25 17:32 ` segher at gcc dot gnu.org 2022-04-25 17:34 ` jakub at gcc dot gnu.org 2022-04-25 17:41 ` segher at gcc dot gnu.org 2022-04-25 17:45 ` segher at gcc dot gnu.org 2022-04-25 17:46 ` seurer at gcc dot gnu.org 2022-04-25 17:48 ` jakub at gcc dot gnu.org 2022-04-25 17:53 ` segher at gcc dot gnu.org 2022-04-25 17:55 ` segher at gcc dot gnu.org 2022-04-25 18:22 ` segher at gcc dot gnu.org 2022-04-25 22:15 ` segher at gcc dot gnu.org 2022-04-26 11:35 ` cvs-commit at gcc dot gnu.org 2022-04-26 16:42 ` jakub 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-105349-4-YGe2z0NQ7N@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).