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 AA8A93858D38; Mon, 12 Feb 2024 18:00:43 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org AA8A93858D38
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1707760843;
	bh=TSetBMnvWF6ykG0h7mGUKGWqOSQtaxSR3XGqB7v2HfA=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=XcejgF49/0PCFAqzgeYdHIIiTAtm3FGPYw5uwxVRQegJacT3vS1f88mJxeew53nOk
	 eWK6PrGDm3c0DyT94OgvhsXuthOSCrxdrQHpcVxyhR3EWNYu1phLxk2ZI5EnE5s6j2
	 yWp0vHaCJtteow0Cq7Sc/voHJBTnUnpFOdiTvHoo=
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/113712] [11/12/13/14 Regression] lto crash: when building
 641.leela_s peek with Example-gcc-linux-x86.cfg (SPEC2017 1.1.9) since
 r10-3311-gff6686d2e5f797
Date: Mon, 12 Feb 2024 18:00:43 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jamborm at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 11.5
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-113712-4-dklVwfMoN0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-113712-4@http.gcc.gnu.org/bugzilla/>
References: <bug-113712-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=3D113712

--- Comment #20 from Martin Jambor <jamborm at gcc dot gnu.org> ---
I have access to the benchmark and building it with -fprofile-generate
it fails for me (with an ICE in add_symbol_to_partition_1) only when I
use -fno-use-linker-plugin and either -std=3Dc++11 or -std=3Dc++03. Using
-std=3Dc++14 also avoids the issue.  In any event, -fno-use-linker-plugin
looks necessary.=