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 1C19A3858D33; Thu,  4 Jan 2024 16:33:18 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1C19A3858D33
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1704385998;
	bh=+7QkficZ2s2I5q+u3edSUsiTmMh7cDtIiC0owlox0I8=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=xuiSjWm1m3zO6pqS+3SqEDZPORvl8DAhSzv9wmtD6r49VIY20Ug4qVZaUVcyQwTEy
	 XvGUHFykx73G3TtxdvueXQkGVlHuE5K5m+hgOZExwopxd2vIKtHZ4HtoddsnZrxoL3
	 GQc1YMR0kxPT1WhXR6nOKzatE2M3/AkzI1Jx/h7w=
From: "patrick at rivosinc dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/113228] [14 Regression] ICE:
 recalculate_side_effects, at gimplify.cc:3347
Date: Thu, 04 Jan 2024 16:33:17 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: patrick at rivosinc dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
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-113228-4-VtkVKtHIBb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-113228-4@http.gcc.gnu.org/bugzilla/>
References: <bug-113228-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=3D113228

--- Comment #10 from Patrick O'Neill <patrick at rivosinc dot com> ---
(In reply to Andrew Pinski from comment #9)
> Oh ok, I was deciding if I should look further into this or let someone e=
lse
> handle it. Since it is from a fuzzer, I am just going to say I don't have
> time to look into this latent bug even though I exposed it :).

Makes sense, I'll start adding a little blurb to future testcases that come
from the fuzzer so people can prioritize accordingly.=