public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "geryemreis at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109678] [13/14 Regression] exponential time behavior on std::variant Date: Tue, 02 May 2023 07:45:40 +0000 [thread overview] Message-ID: <bug-109678-4-8DyvtSxCMA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109678-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109678 --- Comment #2 from Gery Emreis <geryemreis at gmail dot com> --- Its not just about compilation time but also about RAM usage. Compilation of variation of std::variant as in provided example consumes unholy amounts of RAM which in the end makes some files uncompilable on my system, because GCC consumes all available RAM and swap and makes my system hang.
next prev parent reply other threads:[~2023-05-02 7:45 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-29 7:49 [Bug c++/109678] New: " quentin.sabah at gmail dot com 2023-04-29 15:02 ` [Bug c++/109678] [13/14 Regression] " ppalka at gcc dot gnu.org 2023-05-01 21:35 ` jason at gcc dot gnu.org 2023-05-02 6:24 ` rguenth at gcc dot gnu.org 2023-05-02 7:45 ` geryemreis at gmail dot com [this message] 2023-05-02 20:26 ` cvs-commit at gcc dot gnu.org 2023-05-02 20:26 ` cvs-commit at gcc dot gnu.org 2023-05-02 20:26 ` cvs-commit at gcc dot gnu.org 2023-05-03 17:10 ` jason at gcc dot gnu.org 2023-05-04 5:00 ` quentin.sabah at gmail dot com 2023-06-01 11:54 ` redi at gcc dot gnu.org 2023-06-14 21:18 ` pinskia at gcc dot gnu.org 2023-08-11 21:23 ` cvs-commit 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-109678-4-8DyvtSxCMA@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).