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/102069] New: [12 regression] New test case gcc.dg/vect/pr101145_3.c in r12-3136 fails on power 7 Date: Wed, 25 Aug 2021 19:50:52 +0000 [thread overview] Message-ID: <bug-102069-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102069 Bug ID: 102069 Summary: [12 regression] New test case gcc.dg/vect/pr101145_3.c in r12-3136 fails on power 7 Product: gcc Version: 9.4.1 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:3673dcf6d6baeb67bb70ff03d4cb3f92beed0075, r12-3136 make -k check-gcc RUNTESTFLAGS="--target_board=unix'{-m64}' vect.exp=gcc.dg/vect/pr101145_3.c" FAIL: gcc.dg/vect/pr101145_3.c scan-tree-dump-times vect "vectorized 1 loops" 2 FAIL: gcc.dg/vect/pr101145_3.c -flto -ffat-lto-objects scan-tree-dump-times vect "vectorized 1 loops" 2 # of expected passes 4 # of unexpected failures 2 I only see this failure on power 7 for 64 bit. Power 7 has some limitations on vectors that may require the failing parts of the tests to be skipped there.
next reply other threads:[~2021-08-25 19:50 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-25 19:50 seurer at gcc dot gnu.org [this message] 2021-08-26 8:20 ` [Bug target/102069] " guojiufu at gcc dot gnu.org 2021-08-26 8:35 ` rguenth at gcc dot gnu.org 2021-08-26 9:58 ` rguenth at gcc dot gnu.org 2021-12-16 1:54 ` guojiufu 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-102069-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).