public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia 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: Fri, 19 Jan 2024 03:12:33 +0000 [thread overview]
Message-ID: <bug-113495-4-Uobnl4eHo1@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 #8 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Patrick O'Neill from comment #7)
> I believe the memory hog is caused by this:
> https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=gcc/config/riscv/riscv-vsetvl.cc;
> h=2067073185f8c0f398908b164a99b592948e6d2d;
> hb=565935f93a7da629da89b05812a3e8c43287598f#l2427
>
> In the slightly reduced test program I was using to debug there were ~35k
> bb's leading to num_expr being roughly 1 million. vsetvl then makes 35k
> bitmaps of ~1 million bits.
How sparse is this bitmap will be? bitmap instead of sbitmap should be used if
the bitmap is going to be sparse. sbitmap is a fixed sized based on the bitmap
size while bitmap is better for sparse bitmaps as it is implemented as linked
list.
next prev parent reply other threads:[~2024-01-19 3:12 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 [this message]
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
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-Uobnl4eHo1@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).