public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rdapp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/113495] RISC-V: Time and memory awful consumption of SPEC2017 wrf benchmark Date: Mon, 22 Jan 2024 11:42:43 +0000 [thread overview] Message-ID: <bug-113495-4-mlbo2PjupL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113495-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113495 --- Comment #27 from Robin Dapp <rdapp at gcc dot gnu.org> --- Following up on this: I'm seeing the same thing Patrick does. We create a lot of large non-sparse sbitmaps that amount to around 33G in total. I did local experiments replacing all sbitmaps that are not needed for LCM by regular bitmaps. Apart from output differences vs the original version the testsuite is unchanged. As expected, wrf now takes longer to compiler, 8 mins vs 4ish mins before and we still use 2.7G of RAM for this single file (Likely because of the remaining sbitmaps) compared to a max of 1.2ish G that the rest of the commpilation uses. One possibility to get the best of both worlds would be to threshold based on num_bbs * num_exprs. Once we exceed it switch to the bitmap pass, otherwise keep sbitmaps for performance. Messaging with Juzhe offline, his best guess for the LICM time is that he enabled checking for dataflow which slows down this particular compilation by a lot. Therefore it doesn't look like a generic problem.
next prev parent reply other threads:[~2024-01-22 11:42 UTC|newest] Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-19 1:22 [Bug c/113495] New: " juzhe.zhong at rivai dot ai 2024-01-19 1:36 ` [Bug tree-optimization/113495] " juzhe.zhong at rivai dot ai 2024-01-19 1:38 ` juzhe.zhong at rivai dot ai 2024-01-19 1:48 ` juzhe.zhong at rivai dot ai 2024-01-19 1:52 ` juzhe.zhong at rivai dot ai 2024-01-19 1:55 ` [Bug rtl-optimization/113495] " pinskia at gcc dot gnu.org 2024-01-19 1:56 ` juzhe.zhong at rivai dot ai 2024-01-19 3:08 ` patrick at rivosinc dot com 2024-01-19 3:12 ` pinskia at gcc dot gnu.org 2024-01-19 3:14 ` pinskia at gcc dot gnu.org 2024-01-19 3:33 ` juzhe.zhong at rivai dot ai 2024-01-19 3:34 ` juzhe.zhong at rivai dot ai 2024-01-19 3:44 ` juzhe.zhong at rivai dot ai 2024-01-19 3:46 ` juzhe.zhong at rivai dot ai 2024-01-19 3:52 ` juzhe.zhong at rivai dot ai 2024-01-19 3:56 ` pinskia at gcc dot gnu.org 2024-01-19 3:58 ` juzhe.zhong at rivai dot ai 2024-01-19 4:00 ` juzhe.zhong at rivai dot ai 2024-01-19 8:23 ` juzhe.zhong at rivai dot ai 2024-01-19 8:41 ` juzhe.zhong at rivai dot ai 2024-01-19 9:23 ` rguenth at gcc dot gnu.org 2024-01-19 9:24 ` rguenth at gcc dot gnu.org 2024-01-19 9:28 ` juzhe.zhong at rivai dot ai 2024-01-19 9:35 ` kito at gcc dot gnu.org 2024-01-19 10:03 ` cvs-commit at gcc dot gnu.org 2024-01-19 10:05 ` juzhe.zhong at rivai dot ai 2024-01-19 10:22 ` rguenther at suse dot de 2024-01-22 11:42 ` rdapp at gcc dot gnu.org [this message] 2024-01-22 11:51 ` juzhe.zhong at rivai dot ai 2024-01-22 12:00 ` rguenth at gcc dot gnu.org 2024-01-22 13:21 ` juzhe.zhong at rivai dot ai 2024-01-22 15:04 ` juzhe.zhong at rivai dot ai 2024-01-24 0:30 ` cvs-commit at gcc dot gnu.org 2024-01-31 0:29 ` cvs-commit at gcc dot gnu.org 2024-01-31 1:25 ` juzhe.zhong at rivai dot ai
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-113495-4-mlbo2PjupL@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).