public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.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 [thread overview] Message-ID: <bug-109724-4-Ke0djLs87f@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109724-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109724 Sam James <sjames at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marxin at gcc dot gnu.org --- Comment #5 from Sam James <sjames at gcc dot gnu.org> --- (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.
next prev parent reply other threads:[~2023-05-04 6:44 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-04 1:53 [Bug c++/109724] New: [10 regression] Huge memory usage when building qtwebengine's SkOpAngle.cpp sjames at gcc dot gnu.org 2023-05-04 1:55 ` [Bug c++/109724] [10 regression] Huge memory usage when building qtwebengine's SkOpAngle.cpp since r10-11201-g051f78a5c1d699 sjames at gcc dot gnu.org 2023-05-04 2:07 ` sjames at gcc dot gnu.org 2023-05-04 3:11 ` sjames at gcc dot gnu.org 2023-05-04 6:20 ` rguenth at gcc dot gnu.org 2023-05-04 6:44 ` sjames at gcc dot gnu.org [this message] 2023-05-04 7:00 ` rguenth at gcc dot gnu.org 2023-05-04 7:14 ` rguenth at gcc dot gnu.org 2023-05-04 7:34 ` rguenth at gcc dot gnu.org 2023-05-04 7:39 ` rguenth at gcc dot gnu.org 2023-05-04 7:45 ` cvs-commit at gcc dot gnu.org 2023-05-04 7:46 ` cvs-commit at gcc dot gnu.org 2023-05-04 7:46 ` cvs-commit at gcc dot gnu.org 2023-05-04 7:47 ` cvs-commit at gcc dot gnu.org 2023-05-04 7:47 ` cvs-commit at gcc dot gnu.org 2023-05-04 7:48 ` rguenth at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-109724-4-Ke0djLs87f@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).