public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "eggert at cs dot ucla.edu" <gcc-bugzilla@gcc.gnu.org>
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	[thread overview]
Message-ID: <bug-107060-4-ssup7yRtrW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107060-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107060

--- Comment #10 from Paul Eggert <eggert at cs dot ucla.edu> ---
Created attachment 58064
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58064&action=edit
"gunzip u.i" then "gcc -O2 -S -fanalyzer u.i" to see how much memory GCC uses

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 problem,
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 suppose
this is a regression. Maybe there's a new memory leak of some sort? Or perhaps
it's just -fanalyzer doing new checks for GCC 14.

      parent reply	other threads:[~2024-04-29  1:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27 19:20 [Bug analyzer/107060] New: " eggert at cs dot ucla.edu
2022-09-27 20:55 ` [Bug analyzer/107060] " dmalcolm at gcc dot gnu.org
2022-09-27 21:31 ` dmalcolm at gcc dot gnu.org
2022-09-27 22:22 ` dmalcolm at gcc dot gnu.org
2022-09-28 13:57 ` dmalcolm at gcc dot gnu.org
2022-09-28 15:01 ` dmalcolm at gcc dot gnu.org
2022-09-29  8:10 ` rguenth at gcc dot gnu.org
2022-10-05 17:54 ` cvs-commit at gcc dot gnu.org
2022-10-05 18:20 ` dmalcolm at gcc dot gnu.org
2023-03-02 18:26 ` dmalcolm at gcc dot gnu.org
2024-04-29  1:13 ` eggert at cs dot ucla.edu [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-107060-4-ssup7yRtrW@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).