From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 3BD85385C6E0; Thu, 30 Nov 2023 08:39:46 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3BD85385C6E0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1701333587; bh=EtLbMBZmYXrvb33KRCeZDOa8OG+Q287tRTGHNRT1Q3s=; h=From:To:Subject:Date:In-Reply-To:References:From; b=K7Kcw/wl9n8mFeXYdGV8JTVVYDwCypph4x1Vnq33NkweMWRfhQUFtdAosqr8inX60 LzuwT9lwV0fkMhNOAqxIkmMuwBaCxpbou48Mod3X/q82O7ahdMcfN6KIudZTbWV/lh XGdQoLZgLFwWXuwVSaDebRcXb7M+7KjAa7LLsXBY= From: "rguenther at suse dot de" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/112411] ICE: SIGSEGV with --param=min-nondebug-insn-uid=2147483647 on powerpc64le-unknown-linux-gnu Date: Thu, 30 Nov 2023 08:39:43 +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: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenther at suse dot de 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: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D112411 --- Comment #6 from rguenther at suse dot de --- On Thu, 30 Nov 2023, zsojka at seznam dot cz wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D112411 >=20 > --- Comment #5 from Zdenek Sojka --- > Thank you for the evaluation. > > - params affecting inlining or unrolling often cause ICEs due to > function::last_clique wraparound (it's 16bit uint) Ah, do you have a testcase for this? I see we have an assert in IL verification but not really any handling of the overflow itself (there is a way to gracefully handle it though!). A testcase would really be useful (in a new bug).=