public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/112103] New: [14 regression] gcc.target/powerpc/rlwinm-0.c fails after r14-4941-gd1bb9569d70304 Date: Thu, 26 Oct 2023 16:44:50 +0000 [thread overview] Message-ID: <bug-112103-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112103 Bug ID: 112103 Summary: [14 regression] gcc.target/powerpc/rlwinm-0.c fails after r14-4941-gd1bb9569d70304 Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: seurer at gcc dot gnu.org Target Milestone: --- g:d1bb9569d7030490fe7bb35af432f934560d689d, r14-4941-gd1bb9569d70304 make -k check-gcc RUNTESTFLAGS="powerpc.exp=gcc.target/powerpc/rlwinm-0.c" FAIL: gcc.target/powerpc/rlwinm-0.c scan-assembler-times (?n)^\\s+rldicl 3081 FAIL: gcc.target/powerpc/rlwinm-0.c scan-assembler-times (?n)^\\s+rlwinm 3093 # of expected passes 5 # of unexpected failures 2 These changes in code output are OK as neither the original rlwinm nor the rldicl actually have any effect. So in the short term the test case just needs to update its instruction counts. We are tracking something to get rid of the extraneous ops later. seurer@ltcden2-lp1:~/gcc/git/build/gcc-test$ diff rlwinm-0.s.r14-4940 rlwinm-0.s.r14-4941 5371c5371 < rlwinm 3,3,0,0xffff --- > rldicl 3,3,0,32 6089c6089 < rlwinm 3,3,0,0xff --- > rldicl 3,3,0,32 8959c8959 < rlwinm 3,3,0,0xffff --- > rldicl 3,3,0,32 9677c9677 < rlwinm 3,3,0,0xff --- > rldicl 3,3,0,32 12546c12546 < rlwinm 3,3,0,0xffff --- > rldicl 3,3,0,32 13264c13264 < rlwinm 3,3,0,0xff --- > rldicl 3,3,0,32 16131c16131 < rlwinm 3,3,0,0xffff --- > rldicl 3,3,0,32 19715c19715 < rlwinm 3,3,0,0xffff --- > rldicl 3,3,0,32 23298c23298 < rlwinm 3,3,0,0xffff --- > rldicl 3,3,0,32 commit d1bb9569d7030490fe7bb35af432f934560d689d (HEAD) Author: Roger Sayle <roger@nextmovesoftware.com> Date: Thu Oct 26 10:06:59 2023 +0100 PR 91865: Avoid ZERO_EXTEND of ZERO_EXTEND in make_compound_operation.
next reply other threads:[~2023-10-26 16:44 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-26 16:44 seurer at gcc dot gnu.org [this message] 2023-10-26 21:34 ` [Bug target/112103] " roger at nextmovesoftware dot com 2023-10-27 13:03 ` rguenth at gcc dot gnu.org 2023-11-09 18:35 ` segher at gcc dot gnu.org 2023-11-09 18:37 ` segher at gcc dot gnu.org 2024-01-15 13:57 ` rguenth at gcc dot gnu.org 2024-01-19 16:48 ` bergner at gcc dot gnu.org 2024-02-16 19:01 ` jakub at gcc dot gnu.org 2024-02-19 21:42 ` bergner at gcc dot gnu.org 2024-02-19 22:24 ` bergner at gcc dot gnu.org 2024-02-19 22:40 ` bergner at gcc dot gnu.org 2024-02-20 19:45 ` cvs-commit at gcc dot gnu.org 2024-02-20 19:52 ` bergner 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-112103-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).