From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id C4CB738582B7; Fri, 16 Feb 2024 13:52:10 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C4CB738582B7 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1708091530; bh=c2C9xv/b3f9rKgauIAJG0L5ttQ7dNGhV7x/MBHwS6Ts=; h=From:To:Subject:Date:In-Reply-To:References:From; b=x1UauuQVOmT8occDCy46Fsi25A8XNFOe8sBgs6B5/jVtZor3YeiBjAJXQr0yJRP5P sIanz8dMUKcSxjzz/kQuSIXCh4eprbIyS65K36aIN6lq4Tjoyhd1ZSYVE/UR8UdzHy YpiINtV0G6Unf3129u4kjQR87MiDfAy3sQA6E5Iw= From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/44563] GCC uses a lot of RAM when compiling a large numbers of functions Date: Fri, 16 Feb 2024 13:52:04 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: ipa X-Bugzilla-Version: 4.3.4 X-Bugzilla-Keywords: compile-time-hog, memory-hog X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org 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: cf_reconfirmed_on 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=3D44563 Richard Biener changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed|2010-06-17 10:36:48 |2024-2-16 --- Comment #40 from Richard Biener --- Reconfirmed. On for GCC 14 we use about 2GB of ram on x86_64 with -O0 and = 20s. With -O1 that regresses to 60s and a little less peak memory. callgraph ipa passes : 14.18 ( 23%) tree PTA : 16.43 ( 27%)=20 And -O2 memory usage improves further at about the same compile-time.=