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/110740] New: [14 regression] gcc.target/powerpc/p9-vec-length-epil-1.c Date: Wed, 19 Jul 2023 13:39:56 +0000 [thread overview] Message-ID: <bug-110740-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110740 Bug ID: 110740 Summary: [14 regression] gcc.target/powerpc/p9-vec-length-epil-1.c 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:0682a32c026f1e246eb07bb8066abca4636f01d8, r14-2281-g0682a32c026f1e These are instruction count tests which may just need count adjustments. make -k check-gcc RUNTESTFLAGS="powerpc.exp=gcc.target/powerpc/p9-vec-length-epil-1.c" FAIL: gcc.target/powerpc/p9-vec-length-epil-1.c scan-assembler-times \\mlxvl\\M 14 FAIL: gcc.target/powerpc/p9-vec-length-epil-1.c scan-assembler-times \\mstxvl\\M 7 # of expected passes 3 # of unexpected failures 2 commit 0682a32c026f1e246eb07bb8066abca4636f01d8 (HEAD) Author: Richard Biener <rguenther@suse.de> Date: Mon Jul 3 13:59:33 2023 +0200 tree-optimization/110310 - move vector epilogue disabling to analysis phase
next reply other threads:[~2023-07-19 13:39 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-19 13:39 seurer at gcc dot gnu.org [this message] 2023-07-20 5:26 ` [Bug target/110740] " linkw at gcc dot gnu.org 2023-07-20 8:53 ` linkw at gcc dot gnu.org 2023-07-20 8:55 ` linkw at gcc dot gnu.org 2023-07-20 9:02 ` rguenth at gcc dot gnu.org 2023-07-20 9:41 ` rguenth at gcc dot gnu.org 2023-07-20 10:10 ` linkw at gcc dot gnu.org 2023-07-24 6:21 ` cvs-commit at gcc dot gnu.org 2023-08-24 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-110740-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).