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/110831] New: [14 regression] gcc.dg/stack-check-3.c ICEs after r14-2822-g499b8079a6419b
Date: Thu, 27 Jul 2023 16:38:14 +0000 [thread overview]
Message-ID: <bug-110831-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110831
Bug ID: 110831
Summary: [14 regression] gcc.dg/stack-check-3.c ICEs after
r14-2822-g499b8079a6419b
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:499b8079a6419bb8082de062ec30772296c6700c, r14-2822-g499b8079a6419b
make -k check-gcc RUNTESTFLAGS="dg.exp=gcc.dg/stack-check-3.c"
FAIL: gcc.dg/stack-check-3.c (internal compiler error: in to_gcov_type, at
profile-count.h:831)
FAIL: gcc.dg/stack-check-3.c (test for excess errors)
FAIL: gcc.dg/stack-check-3.c scan-rtl-dump-times expand "allocation and probing
residuals" 7
FAIL: gcc.dg/stack-check-3.c scan-rtl-dump-times expand "allocation and probing
in loop" 4
FAIL: gcc.dg/stack-check-3.c scan-rtl-dump-times expand "allocation and probing
in rotated loop" 1
FAIL: gcc.dg/stack-check-3.c scan-rtl-dump-times expand "allocation and probing
inline" 1
FAIL: gcc.dg/stack-check-3.c scan-rtl-dump-times expand "skipped dynamic
allocation and probing loop" 1
# of unexpected failures 7
spawn -ignore SIGHUP /home/seurer/gcc/git/build/gcc-test/gcc/xgcc
-B/home/seurer/gcc/git/build/gcc-test/gcc/ exceptions_enabled3672263.cc
-fdiagnostics-plain-output -Wno-complain-wrong-lang -S -o
exceptions_enabled3672263.s
FAIL: gcc.dg/stack-check-3.c (test for excess errors)
Excess errors:
during RTL pass: expand
dump file: stack-check-3.c.258r.expand
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/stack-check-3.c:25:1:
internal compiler error: in to_gcov_type, at profile-count.h:831
0x10b3e7b7 profile_count::to_gcov_type() const
/home/seurer/gcc/git/gcc-test/gcc/profile-count.h:831
0x10b3e7b7 dump_prediction
/home/seurer/gcc/git/gcc-test/gcc/predict.cc:797
0x10b495bf combine_predictions_for_insn
/home/seurer/gcc/git/gcc-test/gcc/predict.cc:1039
0x10b495bf guess_outgoing_edge_probabilities(basic_block_def*)
/home/seurer/gcc/git/gcc-test/gcc/predict.cc:2356
0x11a4bec7 compute_outgoing_frequencies
/home/seurer/gcc/git/gcc-test/gcc/cfgbuild.cc:692
0x11a4bec7 find_many_sub_basic_blocks(simple_bitmap_def*)
/home/seurer/gcc/git/gcc-test/gcc/cfgbuild.cc:792
0x10520083 execute
/home/seurer/gcc/git/gcc-test/gcc/cfgexpand.cc:6933
commit 499b8079a6419bb8082de062ec30772296c6700c (HEAD)
Author: Jan Hubicka <jh@suse.cz>
Date: Thu Jul 27 15:57:54 2023 +0200
Fix profile_count::apply_probability
next reply other threads:[~2023-07-27 16:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 16:38 seurer at gcc dot gnu.org [this message]
2023-07-27 18:51 ` [Bug other/110831] " seurer at gcc dot gnu.org
2023-07-28 6:18 ` rguenth at gcc dot gnu.org
2023-07-28 6:41 ` hubicka at gcc dot gnu.org
2023-10-17 12:20 ` rguenth at gcc dot gnu.org
2023-10-17 21:32 ` seurer 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-110831-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).