From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 88D213858414; Fri, 26 Apr 2024 01:56:58 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 88D213858414 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1714096618; bh=V9JZbpeLBU3LmnwYOi1WyICevOWGc0sCL9Fl1YV/dA4=; h=From:To:Subject:Date:In-Reply-To:References:From; b=KaeZgHLART9cAAifg+hvHAPQ4wjOdgxOpVgnXmhfqa9DkzmE4YkxGdfcj7f8HpXo1 ge1HrMbgQZD77bzlQ5mi0z4e+vKnOoxmIoGoemwHTd3BrjfeWJUyotym+rsJm8409F EL8SfvNtp3Z9L8kHeUrTpYnOV1T0GVgbbSX4q6n4= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/114858] [11/12/13/14 regression] Compilation Hang and Excessive RAM Consumption in GCC with invalid input Date: Fri, 26 Apr 2024 01:56:58 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: compile-time-hog X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia 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: 11.5 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: everconfirmed short_desc bug_status 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=3D114858 Andrew Pinski changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Summary|[11/12/13/14 regression] |[11/12/13/14 regression] |Compilation Hang and |Compilation Hang and |Excessive RAM Consumption |Excessive RAM Consumption |in GCC |in GCC with invalid input Status|UNCONFIRMED |NEW Last reconfirmed| |2024-04-26 --- Comment #1 from Andrew Pinski --- Confirmed. Looks like a patch which was backported to the GCC 4.8.4 release= is the cause.=