From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 7F0703858414; Tue, 14 Mar 2023 17:57:18 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7F0703858414
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1678816638;
	bh=mMg+O4pPHybXYk+8Bo6ucphEVianow/J7R2e11IRvUI=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=uFZoHnkNQNSVXewB/QbDeAhcceqVRNZw7VQFoqOZiRe92S4QZDWaEv4Ro7P7sQuZ8
	 iURnuS/HydWpDx0ktqBYA+GCXbmTgSCkaWA4shI97yyhTwB0n8YnTiK8nSQT5tlUCS
	 XMWsHyhCv7lRJDT+r0Msx4LTgfr14EBBBzSdctAg=
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/107925] ICE in update_specialized_profile at
 gcc/ipa-cp.cc:5082 for 531.deepsjeng_r benchmark
Date: Tue, 14 Mar 2023 17:57:18 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jamborm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-107925-4-dtUN5TqoEi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-107925-4@http.gcc.gnu.org/bugzilla/>
References: <bug-107925-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D107925

--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Martin Jambor <jamborm@gcc.gnu.org>:

https://gcc.gnu.org/g:1526ecd739fc6a13329abdcbdbf7c2df57c22177

commit r13-6667-g1526ecd739fc6a13329abdcbdbf7c2df57c22177
Author: Martin Jambor <mjambor@suse.cz>
Date:   Tue Mar 14 18:53:16 2023 +0100

    ipa-cp: Improve updating behavior when profile counts have gone bad

    Looking into the behavior of profile count updating in PR 107925, I
    noticed that an option not considered possible was actually happening,
    and - with the guesswork in place to distribute unexplained counts -
    it simply can happen.  Currently it is handled by dropping the counts
    to local estimated zero, whereas it is probably better to leave the
    count as they are but drop the category to GUESSED_GLOBAL0 - which is
    what profile_count::combine_with_ipa_count in a similar case (or so I
    hope :-)

    gcc/ChangeLog:

    2023-02-20  Martin Jambor  <mjambor@suse.cz>

            PR ipa/107925
            * ipa-cp.cc (update_profiling_info): Drop counts of orig_node to
            global0 instead of zeroing when it does not have as many counts=
 as
            it should.=