public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "luoxhu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/98827] [11 regression] gcc.target/powerpc/vsx-builtin-7.c assembler counts off after r11-6857 Date: Tue, 26 Jan 2021 01:40:48 +0000 [thread overview] Message-ID: <bug-98827-4-ztZbzPfEAO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98827-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98827 --- Comment #1 from luoxhu at gcc dot gnu.org --- Strange that I see only xxpermdi fail, should be 4 instead of 12. rldic passes for m64, what's your configuration please? === gcc tests === Schedule of variations: unix/-m32 unix/-m64 Running target unix/-m32 Running /home/luoxhu/workspace/gcc/gcc/testsuite/gcc.target/powerpc/powerpc.exp ... PASS: gcc.target/powerpc/vsx-builtin-7.c (test for excess errors) PASS: gcc.target/powerpc/vsx-builtin-7.c scan-assembler-times \\mrldic\\M 0 PASS: gcc.target/powerpc/vsx-builtin-7.c scan-assembler-times vspltisb 2 PASS: gcc.target/powerpc/vsx-builtin-7.c scan-assembler-times vspltish 2 PASS: gcc.target/powerpc/vsx-builtin-7.c scan-assembler-times vspltisw 2 PASS: gcc.target/powerpc/vsx-builtin-7.c scan-assembler-times xxpermdi 4 === gcc Summary for unix/-m32 === # of expected passes 6 Running target unix/-m64 Running /home/luoxhu/workspace/gcc/gcc/testsuite/gcc.target/powerpc/powerpc.exp ... PASS: gcc.target/powerpc/vsx-builtin-7.c (test for excess errors) PASS: gcc.target/powerpc/vsx-builtin-7.c scan-assembler-times \\mrldic\\M 64 PASS: gcc.target/powerpc/vsx-builtin-7.c scan-assembler-times vspltisb 2 PASS: gcc.target/powerpc/vsx-builtin-7.c scan-assembler-times vspltish 2 PASS: gcc.target/powerpc/vsx-builtin-7.c scan-assembler-times vspltisw 2 PASS: gcc.target/powerpc/vsx-builtin-7.c scan-assembler-times xxpermdi 4 === gcc Summary for unix/-m64 === # of expected passes 6 === gcc Summary === # of expected passes 12 /home/luoxhu/workspace/build/gcc/xgcc version 11.0.0 20210125 (experimental) (GCC) luoxhu@bns:~/workspace/build$ gcc/xgcc -v Using built-in specs. COLLECT_GCC=gcc/xgcc Target: powerpc64-unknown-linux-gnu Configured with: ../gcc/configure --enable-languages=c,c++,fortran --prefix=/home/luoxhu/local/gcc/ --disable-bootstrap --with-cpu=power7 --disable-libsanitizer : (reconfigured) ../gcc/configure --prefix=/home/luoxhu/local/gcc/ --disable-bootstrap --with-cpu=power7 --disable-libsanitizer CC=/opt/gcc81/bin/gcc CXX=/opt/gcc81/bin/g++ --enable-languages=c,c++,fortran,lto --no-create --no-recursion Thread model: posix Supported LTO compression algorithms: zlib gcc version 11.0.0 20210125 (experimental) (GCC)
next prev parent reply other threads:[~2021-01-26 1:40 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-25 21:08 [Bug target/98827] New: " seurer at gcc dot gnu.org 2021-01-26 1:40 ` luoxhu at gcc dot gnu.org [this message] 2021-01-26 8:08 ` [Bug target/98827] " rguenth at gcc dot gnu.org 2021-01-26 15:14 ` seurer at gcc dot gnu.org 2021-01-27 1:45 ` luoxhu at gcc dot gnu.org 2021-01-28 3:35 ` cvs-commit at gcc dot gnu.org 2021-02-26 12:34 ` rguenth 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-98827-4-ztZbzPfEAO@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).