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 other/108519] New: [13 regression] gcc.target/powerpc/pr105586.c fails after r13-5154-g733a1b777f16cd Date: Tue, 24 Jan 2023 15:16:36 +0000 [thread overview] Message-ID: <bug-108519-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108519 Bug ID: 108519 Summary: [13 regression] gcc.target/powerpc/pr105586.c fails after r13-5154-g733a1b777f16cd Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: other Assignee: unassigned at gcc dot gnu.org Reporter: seurer at gcc dot gnu.org Target Milestone: --- g:733a1b777f16cd397b43a242d9c31761f66d3da8, r13-5154-g733a1b777f16cd This test is failing on some powerpc64 LE systems. make -k check-gcc RUNTESTFLAGS="powerpc.exp=gcc.target/powerpc/pr105586.c" FAIL: gcc.target/powerpc/pr105586.c (test for excess errors) # of unexpected failures 1 /home/seurer/gcc/git/build/gcc-test/gcc/xgcc -B/home/seurer/gcc/git/build/gcc-test/gcc/ /home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.target/powerpc/pr105586.c -fdiagnostics-plain-output -mdejagnu-tune=power4 -O2 -fcompare-debug -fno-if-conversion -fno-guess-branch-probability -S -o pr105586.s^M xgcc: error: /home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.target/powerpc/pr105586.c: '-fcompare-debug' failure (length)^M compiler exited with status 1 FAIL: gcc.target/powerpc/pr105586.c (test for excess errors) Excess errors: xgcc: error: /home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.target/powerpc/pr105586.c: '-fcompare-debug' failure (length) commit 733a1b777f16cd397b43a242d9c31761f66d3da8 (HEAD, refs/bisect/bad) Author: Alexander Monakov <amonakov@ispras.ru> Date: Fri Jan 13 21:04:02 2023 +0300 sched-deps: do not schedule pseudos across calls [PR108117]
next reply other threads:[~2023-01-24 15:16 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-24 15:16 seurer at gcc dot gnu.org [this message] 2023-01-24 15:18 ` [Bug rtl-optimization/108519] " rguenth at gcc dot gnu.org 2023-01-25 16:12 ` amonakov at gcc dot gnu.org 2023-01-26 19:21 ` seurer at gcc dot gnu.org 2023-01-26 20:28 ` amonakov at gcc dot gnu.org 2023-02-23 9:12 ` linkw at gcc dot gnu.org 2023-02-23 9:46 ` 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-108519-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).