From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id CAABF3858D28; Thu, 4 May 2023 06:20:08 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CAABF3858D28 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1683181208; bh=CprChzG+gsiXdfL8m9f9UdyiQ5vbvXM095Y+5Yre//k=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Nc8UCbb42nW7v/OjUsEk5TGw1xhuvlUoCkMAaECRbx51gfFqUVp5MQUAQLyGg/D+R NZ7GEdQwd2NfH7wlSCN3bytDQ3jgYcBEKgaBCanJKy2MgPk6Rt0cIlT2eL9W3mIw+D jk8uIcw1uNigclhlcci0E07Eb2PuI+gYJHpBm01Y= From: "rguenth 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:20:08 +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: rguenth 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: keywords bug_status assigned_to target_milestone everconfirmed 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=3D109724 Richard Biener changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |needs-bisection Status|UNCONFIRMED |ASSIGNED Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot = gnu.org Target Milestone|--- |10.5 Ever confirmed|0 |1 Last reconfirmed| |2023-05-04 --- Comment #4 from Richard Biener --- Huh, interesting. Did you by chance verify if GCC 11, 12 or 13 are affected similarly? I wonder if we can bisect what fixed it if not.=