From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 9AB613858C54; Tue, 20 Feb 2024 12:55:14 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9AB613858C54 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1708433714; bh=gb6L/vrS9iv6f3wsa5F9UlMJoPriVDZS96h2Xs1lqvQ=; h=From:To:Subject:Date:In-Reply-To:References:From; b=fGO+FLznbJvxeCnAwRrPjkn45d2HCuKyac+IX52EnhXHS+qKf7/L61li28GnKnnxt 4Otjfj8FYSbd1e68iKnON305kTAyi6ySI0qutBD3oleHw6jhcplrRiApUqHaBMGZIK cD7lWOV4uS9DCifuHqtL3Ant4VXtAz4AyXcuBGgM= From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/36294] gcc exited and told me to report a bug (details follow) Date: Tue, 20 Feb 2024 12:55:13 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 4.2.1 X-Bugzilla-Keywords: compile-time-hog, memory-hog X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED 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: resolution bug_status 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=3D36294 Richard Biener changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #8 from Richard Biener --- GCC 14 takes around 380MB and 14s for me. Nothing sticks out in particular with respect to profile nor memory. The GCC 4.2.1 binary I have around uses 482MB and 18s with PTA using 46% of the compile-time. I can't say 380MB is much better than 482MB but at least we didn't regress and it's now 15 years later and we don't consider 380MB excessive. I'd still say fixed now, the testcase itself isn't particularly interesting= .=