From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 08B5D3858D28; Thu, 29 Sep 2022 08:10:26 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 08B5D3858D28 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1664439026; bh=JwthrKJg7ihecydnbSjlK+n/QYpHdD3zJO5k/laBDhs=; h=From:To:Subject:Date:In-Reply-To:References:From; b=UtkFIHElNN71eHAKLHZtzDQeEUjJ8EQcbOey/wwXpah5kP5njxg/qqOMQ/lwLcnoW 16gwN6Pnxn1cMbdyg+mkfuJWwDMB6WX6nwcJVuV3JhhEUxYHY67vCxySfZwbMrKW0J Ixhv/ixF0tfN4o1ZS5YiLaikUrmjJwbcFpOtEvh8= From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/107060] -fanalyzer unbearably slow when compiling GNU Emacs Date: Thu, 29 Sep 2022 08:10:25 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: analyzer X-Bugzilla-Version: 12.2.1 X-Bugzilla-Keywords: compile-time-hog X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: dmalcolm 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=3D107060 --- Comment #6 from Richard Biener --- One approach (usually taken by GCC ...) is to add --param tunables and hard-limit search depth/width and number-of-FOO to track with providing mea= ns to up those limits. Both to limit compile-time but also memory-usage.=