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 ECE103858C78; Wed, 10 Apr 2024 08:02:07 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org ECE103858C78
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1712736127;
	bh=8EEg69pW9Ci5jQFQ0+EDGkp0xqna9HIx+kHwskaVDY8=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=JOoRW6O1Qe4WUXU/5wvUwHsi9nmn2pDzuOiw4lt40pXvqvX4tUW1YjoDKzwVQ7Lvj
	 nJPC41KKnta+Wubhs9+ufbuuSzvok7RYn3kZO9A86pikEvJXpefYOz9lj5H5MD8v+c
	 bjtYhdwTeUY2t/D6p16E/x8rwZkJ8+Yg4UjyTvDw=
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/114426] [14 regression] ICE when building log4cxx on arm
 (cxx_eval_call_expression, at cp/constexpr.cc:3242) since r14-6507
Date: Wed, 10 Apr 2024 08:02:04 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 14.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-114426-4-IOp13FGyQg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-114426-4@http.gcc.gnu.org/bugzilla/>
References: <bug-114426-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=3D114426

--- Comment #10 from Richard Biener <rguenth at gcc dot gnu.org> ---
As a band-aid, can we turn the gcc_assert into a gcc_checking_assert to make
the issue latent (again) on release branches?  I understand the issue _is_
latent?=