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 13C563858291; Tue,  5 Mar 2024 12:30:45 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 13C563858291
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1709641845;
	bh=SzuQssm4j+L1sux8xfI/LM/FwOUCpa8NvUVaj937IgM=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=bgF2NLkxqYBz9dsWRy38YmzSlS4eT7Ag82n9OGk1nc8sOvHdDDcJdpgzgMAn09sxf
	 z9M2uLaxV2P/6TZgv8VALv/p9pch3KuSVPVAkNJxqLUgi9dHDI2FGoKpLUQvr3MfFw
	 XW2sEQBYne/pvMAkV5bRN2ECFnP8XbKB0qSowBAM=
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/114232] [14 regression] ICE when building rr-5.7.0 with
 LTO on x86
Date: Tue, 05 Mar 2024 12:30:44 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at ucw dot cz
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ubizjak at gmail dot com
X-Bugzilla-Target-Milestone: 14.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-114232-4-sVxrBiuXyI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-114232-4@http.gcc.gnu.org/bugzilla/>
References: <bug-114232-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=3D114232

--- Comment #18 from Jan Hubicka <hubicka at ucw dot cz> ---
optimize_function_for_size_p is not really affected by LTO or non-LTO.=20
It does take into account node->count and node->frequency, which is
updated during IPA, so it may change between early opts and late opts.

I do not think we change it between vectorizer and RTL (or during RTL)
and we can add this to a verifier if it is practical to rely on it (I
can see that vectorizer makes instruction selection choices).

But the problem here is more that optab initializations happens only at
the optimization_node changes and not if we switch from hot function to
cold?=