public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/106345] New: Some ppc64le tests fail with -mcpu=power9 -mtune=power9 Date: Mon, 18 Jul 2022 17:32:26 +0000 [thread overview] Message-ID: <bug-106345-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106345 Bug ID: 106345 Summary: Some ppc64le tests fail with -mcpu=power9 -mtune=power9 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: testsuite Assignee: unassigned at gcc dot gnu.org Reporter: mpolacek at gcc dot gnu.org Target Milestone: --- A few tests fail when GCC is configured with --with-cpu-64=power9 --with-tune-64=power9: gcc.target/powerpc/lhs-3.c gcc.target/powerpc/loop_align.c gcc.target/powerpc/pr92398.p9-.c It would be nice if we could strengthen the tests to pass with -mtune=power9 -mcpu=power9 too. In detail: # gcc -O2 -mdejagnu-cpu=power7 lhs-3.c -S -mtune=power8 # grep ori lhs-3.s ori 2,2,0 but with the power9 default: # gcc -O2 -mdejagnu-cpu=power7 lhs-3.c -S # grep ori lhs-3.s # The second: # gcc loop_align.c -fdiagnostics-plain-output -O2 -mdejagnu-cpu=power7 -falign-functions=16 -fno-unroll-loops -ffat-lto-objects -fno-ident -S -o loop_align.s # grep p2align loop_align.s .p2align 4,,15 .p2align 4,,15 # gcc loop_align.c -fdiagnostics-plain-output -O2 -mdejagnu-cpu=power7 -falign-functions=16 -fno-unroll-loops -ffat-lto-objects -fno-ident -S -o loop_align.s -mtune=power8 # grep p2align loop_align.s .p2align 4,,15 .p2align 5 And the third test: # gcc pr92398.p9-.c -fdiagnostics-plain-output -O2 -mvsx -ffat-lto-objects -fno-ident -S -o pr92398.p9-.s -mtune=power8 -mcpu=power8 # grep -E '(std|not)' pr92398.p9-.s not 4,4 not 5,5 std 4,0(3) std 5,8(3) .section .note.GNU-stack,"",@progbits # gcc pr92398.p9-.c -fdiagnostics-plain-output -O2 -mvsx -ffat-lto-objects -fno-ident -S -o pr92398.p9-.s # grep -E '(std|not)' pr92398.p9-.s .section .note.GNU-stack,"",@progbits
next reply other threads:[~2022-07-18 17:32 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-18 17:32 mpolacek at gcc dot gnu.org [this message] 2022-07-19 6:23 ` [Bug testsuite/106345] " linkw at gcc dot gnu.org 2022-07-20 2:01 ` linkw at gcc dot gnu.org 2022-07-25 5:53 ` cvs-commit at gcc dot gnu.org 2022-07-26 12:13 ` linkw at gcc dot gnu.org 2022-08-02 3:53 ` cvs-commit at gcc dot gnu.org 2022-08-02 3:56 ` cvs-commit at gcc dot gnu.org 2022-08-02 3:58 ` cvs-commit at gcc dot gnu.org 2022-09-07 1:38 ` cvs-commit at gcc dot gnu.org 2022-09-13 5:21 ` cvs-commit at gcc dot gnu.org 2022-09-13 5:22 ` cvs-commit at gcc dot gnu.org 2022-09-13 6:23 ` cvs-commit at gcc dot gnu.org 2022-09-13 6:24 ` 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-106345-4@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).