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 target/102146] [11 regression] several test cases fails after r11-8940 Date: Thu, 07 Apr 2022 08:50:03 +0000 [thread overview] Message-ID: <bug-102146-4-Tczm0Rzc88@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 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Looking at my 6 days old powerpc64le-linux testresults, I see from gcc.target/powerpc/ FAILures FAIL: gcc.target/powerpc/compress-float-ppc-pic.c scan-assembler lfs FAIL: gcc.target/powerpc/compress-float-ppc.c scan-assembler lfs FAIL: gcc.target/powerpc/fusion-p10-stst.c scan-assembler-times std 4,8\\\\(3\\\\)\\\\n\\\\tstd 6,16\\\\(3\\\\) 1 FAIL: gcc.target/powerpc/fusion-p10-stst.c scan-assembler-times stfd 1,8\\\\(3\\\\)\\\\n\\\\tstfd 3,16\\\\(3\\\\) 1 FAIL: gcc.target/powerpc/fusion-p10-stst.c scan-assembler-times stw 4,4\\\\(3\\\\)\\\\n\\\\tstw 6,8\\\\(3\\\\) 1 FAIL: gcc.target/powerpc/lhs-1.c scan-assembler-times nop 3 FAIL: gcc.target/powerpc/lhs-2.c scan-assembler ori 1,1,0 FAIL: gcc.target/powerpc/pr56605.c scan-rtl-dump-times combine "\\\\(compare:CC \\\\((?:and|zero_extend):(?:DI) \\\\((?:sub)?reg:[SD]I" 1 FAIL: gcc.target/powerpc/prefix-no-update.c scan-assembler-times \\\\mlwz\\\\M 2 FAIL: gcc.target/powerpc/prefix-no-update.c scan-assembler-times \\\\mplwz\\\\M 2 FAIL: gcc.target/powerpc/prefix-no-update.c scan-assembler-times \\\\mpstw\\\\M 2 FAIL: gcc.target/powerpc/prefix-no-update.c scan-assembler-times \\\\mstw\\\\M 2 FAIL: gcc.target/powerpc/rlwimi-2.c scan-assembler-times (?n)^\\\\s+[a-z] 20217 FAIL: gcc.target/powerpc/rs6000-fpint.c scan-assembler-not stfiwx Comparing with GCC 11.1.0 results, that is +FAIL: gcc.target/powerpc/fusion-p10-stst.c scan-assembler-times std 4,8\\\\(3\\\\)\\\\n\\\\tstd 6,16\\\\(3\\\\) 1 +FAIL: gcc.target/powerpc/fusion-p10-stst.c scan-assembler-times stfd 1,8\\\\(3\\\\)\\\\n\\\\tstfd 3,16\\\\(3\\\\) 1 +FAIL: gcc.target/powerpc/fusion-p10-stst.c scan-assembler-times stw 4,4\\\\(3\\\\)\\\\n\\\\tstw 6,8\\\\(3\\\\) 1 +FAIL: gcc.target/powerpc/pr56605.c scan-rtl-dump-times combine "\\\\(compare:CC \\\\((?:and|zero_extend):(?:DI) \\\\((?:sub)?reg:[SD]I" 1 +FAIL: gcc.target/powerpc/prefix-no-update.c scan-assembler-times \\\\mlwz\\\\M 2 +FAIL: gcc.target/powerpc/prefix-no-update.c scan-assembler-times \\\\mplwz\\\\M 2 +FAIL: gcc.target/powerpc/prefix-no-update.c scan-assembler-times \\\\mpstw\\\\M 2 +FAIL: gcc.target/powerpc/prefix-no-update.c scan-assembler-times \\\\mstw\\\\M 2 regression.
next prev parent reply other threads:[~2022-04-07 8:50 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 [this message] 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 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-Tczm0Rzc88@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).