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 testsuite/109145] New: new test case gcc.dg/tree-ssa/forwprop-39.c from r13-6624-geb337d28c32b1b fails Date: Wed, 15 Mar 2023 14:25:34 +0000 [thread overview] Message-ID: <bug-109145-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109145 Bug ID: 109145 Summary: new test case gcc.dg/tree-ssa/forwprop-39.c from r13-6624-geb337d28c32b1b fails Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: testsuite Assignee: unassigned at gcc dot gnu.org Reporter: seurer at gcc dot gnu.org Target Milestone: --- g:eb337d28c32b1b460cc85b3c00f8418ca535c77b, r13-6624-geb337d28c32b1b I am seeing this failing only on our older power 7 machines. make -k check-gcc RUNTESTFLAGS="tree-ssa.exp=gcc.dg/tree-ssa/forwprop-39.c" FAIL: gcc.dg/tree-ssa/forwprop-39.c (test for excess errors) FAIL: gcc.dg/tree-ssa/forwprop-39.c scan-tree-dump-not forwprop1 "COMPLEX_EXPR" FAIL: gcc.dg/tree-ssa/forwprop-39.c scan-tree-dump-not optimized "REALPART_EXPR" # of unexpected failures 3 commit eb337d28c32b1b460cc85b3c00f8418ca535c77b Author: Richard Biener <rguenther@suse.de> Date: Tue Mar 7 11:04:55 2023 +0100 tree-optimization/109046 - re-combine complex loads
next reply other threads:[~2023-03-15 14:25 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-15 14:25 seurer at gcc dot gnu.org [this message] 2023-03-15 14:45 ` [Bug testsuite/109145] " rguenth at gcc dot gnu.org 2023-03-16 14:32 ` seurer at gcc dot gnu.org 2023-03-16 16:06 ` hp at gcc dot gnu.org 2023-03-16 17:25 ` seurer at gcc dot gnu.org 2023-03-16 17:26 ` seurer at gcc dot gnu.org 2023-03-16 17:41 ` jakub at gcc dot gnu.org 2023-03-16 17:51 ` jakub at gcc dot gnu.org 2023-03-16 18:21 ` seurer at gcc dot gnu.org 2023-03-16 18:26 ` pinskia at gcc dot gnu.org 2023-03-17 8:47 ` rguenth at gcc dot gnu.org 2023-03-17 8:58 ` cvs-commit 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-109145-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).