From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 8AFE83858D32; Thu, 30 Nov 2023 08:32:18 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8AFE83858D32 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1701333138; bh=KzMTex6hNgQC+y2BI6qgIpe0Kqnq/0DrKQW4WmuqHQ8=; h=From:To:Subject:Date:In-Reply-To:References:From; b=A1IZsZv2UD4nBwkhIHt5SwgZQO0pFBUD6Ex0XjjqIy+REAnJ1vTqcQEbSpY9TAWmC uibBEm3Q4MSURwPF2oC9f95sl7CXidQvcaxprzmXAfbikUL7QKnD3/D7X2aqrApUIo PwU2RUeMyNOlYkoAUpEmOzFnGH8MXtrcA6CjUvpc= From: "zsojka at seznam dot cz" 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:32:16 +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: zsojka at seznam dot cz 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 #5 from Zdenek Sojka --- Thank you for the evaluation. I am not reporting ICEs (assertion / checking failures) due to overflows ca= used by extreme --param values: - this param is typically causing ICEs due to insn UID overflow - params affecting inlining or unrolling often cause ICEs due to function::last_clique wraparound (it's 16bit uint) - generally, I am trying to consider if a real-world scenario could trigger= the ICE This is different, since there is no assertion or checking failure, but a segmentation fault; that is uncommon.=