From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id AE5E638582A4; Wed, 28 Sep 2022 13:57:29 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org AE5E638582A4 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1664373449; bh=5Lq4ity01GREah4ADQUR4b9sRvmsdAGXqbmVaQrImA4=; h=From:To:Subject:Date:In-Reply-To:References:From; b=XGEhoQF1/sPIxxvA2IKVdC3LbIA5G4Js4OZusmS8iGiWM/XOJ068mGCbT57NKYHCM haGlZMOyyAnEvNaCXlmKWzstTsW0zdCgIHBKTAhF3v52+4VHoFHe72aUAxgaHMuZpR 4ROe3bmz/2HLDExc4AHKAsV8O8x0pgPI0a7ehLvE= From: "dmalcolm at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/107060] -fanalyzer unbearably slow when compiling GNU Emacs Date: Wed, 28 Sep 2022 13:57:29 +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: dmalcolm 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 #4 from David Malcolm --- (In reply to David Malcolm from comment #3) > perf shows that 64% of the time is taken by this ctor: > shortest_paths::shortest_paths This is in the "find shortest feasible path for a diagnostic" code. FWIW, adding -fno-analyzer-feasibility reduces the time for me from 10 minu= tes to about 4.5 minutes (better, but still far too slow), and makes it emit a false positive. I'm investigating where the slowdowns are.=