public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/35608] limit-structnest.c fails due to O(n^2) memory usage in record_component_alias
Date: Tue, 20 Feb 2024 12:48:11 +0000	[thread overview]
Message-ID: <bug-35608-4-VdXAteNkkg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-35608-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35608

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|2009-11-03 12:18:41         |2024-2-20

--- Comment #11 from Richard Biener <rguenth at gcc dot gnu.org> ---
GCC 14 shows, at -O2 with LIM4/RBR4 (the testcases setting)

0.55user 0.18system 0:00.73elapsed 100%CPU (0avgtext+0avgdata
798332maxresident)k
0inputs+8outputs (0major+195627minor)pagefaults 0swaps

and with LIM5/RBR5 it blows 64GB.  So here's LIM3/RBR3 as comparison:

0.00user 0.02system 0:00.38elapsed 8%CPU (0avgtext+0avgdata 30988maxresident)k
53680inputs+104outputs (74major+3608minor)pagefaults 0swaps

re-confirmed and it's the original issue still, though the implementation
detail of record_alias_subset rather record_component_aliases.
record_alias_subset records childrens of the subset as immediate subset
transitively.

           reply	other threads:[~2024-02-20 12:48 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <bug-35608-4@http.gcc.gnu.org/bugzilla/>]

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-35608-4-VdXAteNkkg@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: link
Be 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).