From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 24F4F3858C42; Mon, 29 Apr 2024 01:13:24 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 24F4F3858C42 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1714353204; bh=/qtsQmvh1RLcYYc9YLy0V9lxEo1tIE8SOsH/7TQMM9o=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Ze+c2xKgkI+pHXv18kvmlcoW9Jcxn/jTTP77dzSsSnJt0g0Yi5SLfT6A4xxfuoJ1d JJkahq/ZWeWtnVmNIomoiBo9HSS3PcRVKWazDEj8Sgcx0kD2mtMhUr4NMm+7ufmzRh UU4AJBSCizxWKxRt8nunxeSGPbcxwEv64CoB2xJM= From: "eggert at cs dot ucla.edu" To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/107060] -fanalyzer unbearably slow when compiling GNU Emacs Date: Mon, 29 Apr 2024 01:13:21 +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: eggert at cs dot ucla.edu 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: attachments.created 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 #10 from Paul Eggert --- Created attachment 58064 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D58064&action=3Dedit "gunzip u.i" then "gcc -O2 -S -fanalyzer u.i" to see how much memory GCC us= es I'm having more trouble with this when using gcc (GCC) 14.0.1 20240411 (Red= Hat 14.0.1-0) on x86-64. I am now getting "gcc: fatal error: Killed signal terminated program cc1" when compiling Emacs xdisp.c. To reproduce the prob= lem, run gunzip u.i gcc -O2 -S -fanalyzer u.i with the attached file u.i.gz. GCC keeps allocating more and more virtual memory, almost all via brk (wouldn't mmap be better? but I digress) until it goes past 10 GB and exhausts my little machine's swap space (7.7G of zram). I didn't see this problem with GCC 13 on Fedora 39, so in some sense I supp= ose this is a regression. Maybe there's a new memory leak of some sort? Or perh= aps it's just -fanalyzer doing new checks for GCC 14.=