public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/111328] [14 Regression] ICE: verify_flow_info failed since r14-3459-g0c78240fd7d
Date: Thu, 07 Mar 2024 23:21:12 +0000 [thread overview]
Message-ID: <bug-111328-4-8QaITVFy2v@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111328-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111328
Jeffrey A. Law <law at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|WAITING |RESOLVED
CC| |law at gcc dot gnu.org
--- Comment #2 from Jeffrey A. Law <law at gcc dot gnu.org> ---
Fixed by:
commit cc50337215535e17f1caa5eae34eaa650223c96b (HEAD, refs/bisect/bad)
Author: Eugene Rozenfeld <erozen@microsoft.com>
Date: Fri Sep 15 18:12:47 2023 -0700
Fixes for profile count/probability maintenance
Verifier checks have recently been strengthened to check that
all counts and probabilities are initialized. The checks fired
during autoprofiledbootstrap build and this patch fixes it.
Tested on x86_64-pc-linux-gnu.
gcc/ChangeLog:
* auto-profile.cc (afdo_calculate_branch_prob): Fix count
comparisons
* tree-vect-loop-manip.cc (vect_do_peeling): Guard against zero
count
when scaling loop profile
prev parent reply other threads:[~2024-03-07 23:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 15:51 [Bug c/111328] New: " shaohua.li at inf dot ethz.ch
2023-09-07 19:08 ` [Bug tree-optimization/111328] " pinskia at gcc dot gnu.org
2023-10-17 12:52 ` [Bug tree-optimization/111328] [14 Regression] " rguenth at gcc dot gnu.org
2024-03-07 23:21 ` law at gcc dot gnu.org [this message]
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-111328-4-8QaITVFy2v@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).