public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/108738] compile-time and memory-hog in mdreorg
Date: Wed, 15 Feb 2023 07:28:28 +0000 [thread overview]
Message-ID: <bug-108738-4-J3t5sYzHW4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108738-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108738
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:ec23e9e25eb64bb066dc408fd498861b8587bec8
commit r13-5994-gec23e9e25eb64bb066dc408fd498861b8587bec8
Author: Richard Biener <rguenther@suse.de>
Date: Thu Feb 9 11:03:25 2023 +0100
target/108738 - STV bitmap operations compile-time hog
When the set of candidates becomes very large then repeated
bit checks on it during the build of an actual chain can become
slow because of the O(n) nature of bitmap tests. The following
switches the candidates bitmaps to the tree representation before
building the chains to get O(log n) amortized behavior.
For the testcase at hand this improves STV time by 50%.
PR target/108738
* config/i386/i386-features.cc (convert_scalars_to_vector):
Switch candidates bitmaps to tree view before building the chains.
next prev parent reply other threads:[~2023-02-15 7:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 8:10 [Bug target/108738] New: " rguenth at gcc dot gnu.org
2023-02-09 8:47 ` [Bug target/108738] " rguenth at gcc dot gnu.org
2023-02-09 9:11 ` rguenth at gcc dot gnu.org
2023-02-09 9:24 ` rguenth at gcc dot gnu.org
2023-02-09 12:48 ` rguenth at gcc dot gnu.org
2023-02-15 7:28 ` cvs-commit at gcc dot gnu.org [this message]
2023-02-15 7:28 ` cvs-commit at gcc dot gnu.org
2023-03-02 11:38 ` rguenth at gcc dot gnu.org
2023-03-03 7:31 ` cvs-commit at gcc dot gnu.org
2023-03-03 7:33 ` rguenth 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-108738-4-J3t5sYzHW4@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).