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 tree-optimization/113910] [12 Regression] Factor 15 slowdown compiling AMDGPUDisassembler.cpp on SPARC Date: Tue, 04 Jun 2024 08:07:53 +0000 [thread overview] Message-ID: <bug-113910-4-AZ5kkYdZtH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113910-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113910 --- Comment #19 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:db0f236aa1c30f703ff564960bd9f3dbd747ea7b commit r12-10490-gdb0f236aa1c30f703ff564960bd9f3dbd747ea7b Author: Richard Biener <rguenther@suse.de> Date: Wed Feb 14 12:33:13 2024 +0100 tree-optimization/113910 - huge compile time during PTA For the testcase in PR113910 we spend a lot of time in PTA comparing bitmaps for looking up equivalence class members. This points to the very weak bitmap_hash function which effectively hashes set and a subset of not set bits. The major problem with it is that it simply truncates the BITMAP_WORD sized intermediate hash to hashval_t which is unsigned int, effectively not hashing half of the bits. This reduces the compile-time for the testcase from tens of minutes to 42 seconds and PTA time from 99% to 46%. PR tree-optimization/113910 * bitmap.cc (bitmap_hash): Mix the full element "hash" to the hashval_t hash. (cherry picked from commit ad7a365aaccecd23ea287c7faaab9c7bd50b944a)
next prev parent reply other threads:[~2024-06-04 8:07 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-13 15:37 [Bug tree-optimization/113910] New: [12/13/14 regression] " ro at gcc dot gnu.org 2024-02-13 15:38 ` [Bug tree-optimization/113910] " ro at gcc dot gnu.org 2024-02-13 15:39 ` ro at gcc dot gnu.org 2024-02-13 15:40 ` ro at gcc dot gnu.org 2024-02-13 15:55 ` pinskia at gcc dot gnu.org 2024-02-13 16:04 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-02-14 9:36 ` rguenth at gcc dot gnu.org 2024-02-14 9:37 ` rguenth at gcc dot gnu.org 2024-02-14 9:44 ` rguenth at gcc dot gnu.org 2024-02-14 10:05 ` rguenth at gcc dot gnu.org 2024-02-14 10:26 ` rguenth at gcc dot gnu.org 2024-02-14 11:32 ` rguenth at gcc dot gnu.org 2024-02-14 11:41 ` rguenth at gcc dot gnu.org 2024-02-14 14:51 ` rguenth at gcc dot gnu.org 2024-02-14 14:51 ` cvs-commit at gcc dot gnu.org 2024-02-14 15:11 ` [Bug tree-optimization/113910] [12/13 Regression] " rguenth at gcc dot gnu.org 2024-02-14 20:07 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-02-15 10:43 ` rguenth at gcc dot gnu.org 2024-02-16 12:57 ` rguenth at gcc dot gnu.org 2024-03-21 11:49 ` cvs-commit at gcc dot gnu.org 2024-06-04 8:07 ` cvs-commit at gcc dot gnu.org [this message] 2024-06-04 8:09 ` [Bug tree-optimization/113910] [12 " 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-113910-4-AZ5kkYdZtH@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).