public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub 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: Mon, 25 Apr 2022 17:48:08 +0000 [thread overview] Message-ID: <bug-105349-4-4VgR8FuoRQ@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 #12 from Jakub Jelinek <jakub at gcc dot gnu.org> --- I said that above, -mdejagnu-cpu=power10 isn't passed to the effective target snippet compilation, so it doesn't test whether the test with -mdejagnu-cpu=power10 will be power10, but rather tests whether the compiler is configured to default to -mcpu=power10 or perhaps whether this is --target_board=unix/-mcpu=power10 testing: Executing on host: /usr/src/gcc/objp16/gcc/xgcc -B/usr/src/gcc/objp16/gcc/ -m32 -fdiagnostics-plain-output -mcpu=power10 -c -o power10_ok1793558.o power10_ok1793558.c (timeout = 300) spawn -ignore SIGHUP /usr/src/gcc/objp16/gcc/xgcc -B/usr/src/gcc/objp16/gcc/ -m32 -fdiagnostics-plain-output -mcpu=power10 -c -o power10_ok1793558.o power10_ok1793558.c Executing on host: /usr/src/gcc/objp16/gcc/xgcc -B/usr/src/gcc/objp16/gcc/ /usr/src/gcc/gcc/testsuite/gcc.target/powerpc/bswap-brw.c -m32 -fdiagnostics-plain-output -O2 -mdejagnu -cpu=power10 -ffat-lto-objects -fno-ident -S -o bswap-brw.s (timeout = 300) spawn -ignore SIGHUP /usr/src/gcc/objp16/gcc/xgcc -B/usr/src/gcc/objp16/gcc/ /usr/src/gcc/gcc/testsuite/gcc.target/powerpc/bswap-brw.c -m32 -fdiagnostics-plain-output -O2 -mdejagnu-c pu=power10 -ffat-lto-objects -fno-ident -S -o bswap-brw.s Executing on host: /usr/src/gcc/objp16/gcc/xgcc -B/usr/src/gcc/objp16/gcc/ exceptions_enabled1793558.cc -m32 -fdiagnostics-plain-output -S -o exceptions_enabled1793558.s (time out = 300) spawn -ignore SIGHUP /usr/src/gcc/objp16/gcc/xgcc -B/usr/src/gcc/objp16/gcc/ exceptions_enabled1793558.cc -m32 -fdiagnostics-plain-output -S -o exceptions_enabled1793558.s PASS: gcc.target/powerpc/bswap-brw.c (test for excess errors) PASS: gcc.target/powerpc/bswap-brw.c scan-assembler \\mbrw\\M Executing on host: /usr/src/gcc/objp16/gcc/xgcc -B/usr/src/gcc/objp16/gcc/ arch_pwr101793558.c -m32 -fdiagnostics-plain-output -S -o arch_pwr101793558.s (timeout = 300) spawn -ignore SIGHUP /usr/src/gcc/objp16/gcc/xgcc -B/usr/src/gcc/objp16/gcc/ arch_pwr101793558.c -m32 -fdiagnostics-plain-output -S -o arch_pwr101793558.s arch_pwr101793558.c:3:18: error: #error does not have power10 support. compiler exited with status 1 FAIL: gcc.target/powerpc/bswap-brw.c scan-assembler \\mxxbrw\\M
next prev parent reply other threads:[~2022-04-25 17:48 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 ` [Bug testsuite/105349] " segher at gcc dot gnu.org 2022-04-24 14:35 ` 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 [this message] 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-4VgR8FuoRQ@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).