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++/95264] Infinite Loop When Compiling Templated C++ code at -O1 and above Date: Fri, 22 May 2020 09:35:00 +0000 [thread overview] Message-ID: <bug-95264-4-xGVSLIwkV5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95264-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95264 --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- We're then inlining some more costing another ~5GB ontop of the early optimization memory use of ~5GB (might be other IPA transforms than inlining as well). The big function is meanwhile 2 million basic blocks... update-SSA and friends are no fun here (the function with 2 million BBs is eval_orthob). Ah, you use [[gnu::flatten]] on that - so isn't it just what you asked for? I wonder if Clang implements that at all. Note the issue with -fvar-tracking* and -g and large functions is known...
next prev parent reply other threads:[~2020-05-22 9:35 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-21 22:08 [Bug c++/95264] New: " freddie at witherden dot org 2020-05-22 9:14 ` [Bug c++/95264] " rguenth at gcc dot gnu.org 2020-05-22 9:35 ` rguenth at gcc dot gnu.org [this message] 2020-05-22 9:44 ` rguenth at gcc dot gnu.org 2020-05-22 9:55 ` rguenth at gcc dot gnu.org 2020-05-22 10:19 ` rguenth at gcc dot gnu.org 2020-05-22 11:13 ` freddie at witherden dot org 2020-05-22 11:34 ` rguenther at suse dot de 2020-05-22 11:49 ` freddie at witherden dot org 2021-10-02 6:00 ` [Bug ipa/95264] " pinskia 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-95264-4-xGVSLIwkV5@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).