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/106872] New: [13 regression] gcc.dg/uninit-pred-12.c fails after r13-2500-g0a4a2667dc115c Date: Wed, 07 Sep 2022 15:20:39 +0000 [thread overview] Message-ID: <bug-106872-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106872 Bug ID: 106872 Summary: [13 regression] gcc.dg/uninit-pred-12.c fails after r13-2500-g0a4a2667dc115c 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:0a4a2667dc115ca73b552fcabf8570620dfbe55f, r13-2500-g0a4a2667dc115c make -k check-gcc RUNTESTFLAGS="dg.exp=gcc.dg/uninit-pred-12.c" FAIL: gcc.dg/uninit-pred-12.c scan-tree-dump uninit1 "AND \\(NOT \\(ivtmp" # of expected passes 2 # of unexpected failures 1 commit 0a4a2667dc115ca73b552fcabf8570620dfbe55f (HEAD, refs/bisect/bad) Author: Richard Biener <rguenther@suse.de> Date: Tue Sep 6 13:46:00 2022 +0200 tree-optimization/106754 - fix compute_control_dep_chain defect
next reply other threads:[~2022-09-07 15:20 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-07 15:20 seurer at gcc dot gnu.org [this message] 2022-09-08 10:00 ` [Bug other/106872] " rguenth at gcc dot gnu.org 2022-09-08 11:00 ` [Bug testsuite/106872] " rguenth at gcc dot gnu.org 2022-09-08 11:02 ` cvs-commit at gcc dot gnu.org 2022-09-08 11:02 ` rguenth 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-106872-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).