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/110628] New: [14 regression] gcc.dg/tree-ssa/update-threading.c fails after r14-2383-g768f00e3e84123
Date: Tue, 11 Jul 2023 12:50:30 +0000 [thread overview]
Message-ID: <bug-110628-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110628
Bug ID: 110628
Summary: [14 regression] gcc.dg/tree-ssa/update-threading.c
fails after r14-2383-g768f00e3e84123
Product: gcc
Version: 14.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:768f00e3e84123e8d0f1bf28a3b2e0b7995402f1, r14-2383-g768f00e3e84123
make -k check-gcc
RUNTESTFLAGS="tree-ssa.exp=gcc.dg/tree-ssa/update-threading.c"
FAIL: gcc.dg/tree-ssa/update-threading.c scan-tree-dump-times optimized
"Invalid sum" 0
# of expected passes 1
# of unexpected failures 1
commit 768f00e3e84123e8d0f1bf28a3b2e0b7995402f1 (HEAD)
Author: Jan Hubicka <jh@suse.cz>
Date: Fri Jul 7 19:16:59 2023 +0200
Fix some profile consistency testcases
next reply other threads:[~2023-07-11 12:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 12:50 seurer at gcc dot gnu.org [this message]
2023-07-11 13:06 ` [Bug tree-optimization/110628] " rguenth at gcc dot gnu.org
2023-07-11 14:42 ` hubicka at gcc dot gnu.org
2023-07-11 14:51 ` seurer at gcc dot gnu.org
2023-07-13 13:13 ` hubicka at ucw dot cz
2023-07-17 23:02 ` seurer at gcc dot gnu.org
2023-08-15 16:23 ` hp at gcc dot gnu.org
2023-08-17 14:52 ` hubicka at ucw dot cz
2023-08-24 1:14 ` hp at gcc dot gnu.org
2023-08-24 12:03 ` hubicka at ucw dot cz
2023-08-24 14:54 ` hp at gcc dot gnu.org
2023-08-25 1:22 ` hp at gcc dot gnu.org
2024-03-07 23:29 ` law at gcc dot gnu.org
2024-05-07 7:41 ` [Bug tree-optimization/110628] [14/15 " 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-110628-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: link
Be 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).