From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 53E753858D28; Thu, 4 May 2023 06:44:39 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 53E753858D28 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1683182680; bh=NC9zJtbCmbD5ljNlrRRKJnZTdT7o6LjQBAM+g9N2+RA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=JkclMLTbkZXfOAQcVjDszVFMnUQJrfOGbU7x5ibnmQtzLC/vHev+ds0mpnnni8fTg kxI2JvftptqJerdnjX/v2ER75Ja4y0xhwNoICCT0/TAYO34+N69JtGky1crdGUUIdG Q4avKkQ/LEsKTEQrU4lFw8BlYALNEDjmYkTvd5NM= From: "sjames at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109724] [10 regression] Huge memory usage when building qtwebengine's SkOpAngle.cpp since r10-11201-g051f78a5c1d699 Date: Thu, 04 May 2023 06:44:39 +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: 10.4.1 X-Bugzilla-Keywords: compile-time-hog, memory-hog, needs-bisection X-Bugzilla-Severity: normal X-Bugzilla-Who: sjames at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org X-Bugzilla-Target-Milestone: 10.5 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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=3D109724 Sam James changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marxin at gcc dot gnu.org --- Comment #5 from Sam James --- (In reply to Richard Biener from comment #4) > Did you by chance verify if GCC 11, 12 or 13 are affected similarly? releases/{11,12,13} are fine. > I wonder if we can bisect what fixed it if not. The 11.1 and 12.1 tags are fine too. I'm worried that it didn't ever exist on trunk and is a combination of backports manifesting badly. I don't remember it happening on any of the branches either, and given how common a package qtwebengine is, I'm confident we would've noticed if it manifested on any of the release/* branches for an extended period at least= .=