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++/101163] slow compilation for huge classes (>20k members functions) Date: Tue, 22 Jun 2021 11:07:42 +0000 [thread overview] Message-ID: <bug-101163-4-MXnQWYni2N@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101163-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101163 --- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> --- OTOH the "binary search tables" are vectors which of course makes them hard to build incrementally since insert is O(n). It might be possible to use a hash-table in the storage place of said vector storage during construction and then compact that down to the current binary search vector when finalized.
next prev parent reply other threads:[~2021-06-22 11:07 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-22 9:19 [Bug c++/101163] New: slow compilation for huge classes (>20k members) rbuergel at web dot de 2021-06-22 9:27 ` [Bug c++/101163] " rbuergel at web dot de 2021-06-22 10:05 ` rguenth at gcc dot gnu.org 2021-06-22 10:11 ` jakub at gcc dot gnu.org 2021-06-22 11:07 ` rguenth at gcc dot gnu.org [this message] 2021-06-24 10:09 ` [Bug c++/101163] slow compilation for huge classes (>20k members functions) rbuergel at web dot de 2021-06-24 11:12 ` jakub 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-101163-4-MXnQWYni2N@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).