public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "krebbel at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/101523] Huge number of combine attempts Date: Thu, 07 Mar 2024 15:51:26 +0000 [thread overview] Message-ID: <bug-101523-4-Apk96rzAZi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101523-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101523 --- Comment #22 from Andreas Krebbel <krebbel at gcc dot gnu.org> --- I did a git bisect which ended up pointing at this commit, somewhere between GCC 8 and 9: commit c4c5ad1d6d1e1e1fe7a1c2b3bb097cc269dc7306 (bad) Author: Segher Boessenkool <segher@kernel.crashing.org> Date: Mon Jul 30 15:18:17 2018 +0200 combine: Allow combining two insns to two insns This patch allows combine to combine two insns into two. This helps in many cases, by reducing instruction path length, and also allowing further combinations to happen. PR85160 is a typical example of code that it can improve. This patch does not allow such combinations if either of the original instructions was a simple move instruction. In those cases combining the two instructions increases register pressure without improving the code. With this move test register pressure does no longer increase noticably as far as I can tell. (At first I also didn't allow either of the resulting insns to be a move instruction. But that is actually a very good thing to have, as should have been obvious). With this command line: cc1plus -O2 -march=z196 -fpreprocessed Q111-8.ii -quiet before: 20s compile-time and 21846 total combine attempts after: > 5min compile-time and 43175686 total combine attempts
next prev parent reply other threads:[~2024-03-07 15:51 UTC|newest] Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-20 9:35 [Bug rtl-optimization/101523] New: " krebbel at gcc dot gnu.org 2021-07-20 9:41 ` [Bug rtl-optimization/101523] " krebbel at gcc dot gnu.org 2021-07-20 9:42 ` krebbel at gcc dot gnu.org 2021-07-20 21:27 ` segher at gcc dot gnu.org 2024-02-24 5:45 ` krebbel at gcc dot gnu.org 2024-02-25 10:53 ` segher at gcc dot gnu.org 2024-02-25 15:06 ` segher at gcc dot gnu.org 2024-03-02 18:43 ` sarah.kriesch at opensuse dot org 2024-03-02 21:04 ` sjames at gcc dot gnu.org 2024-03-03 19:32 ` segher at gcc dot gnu.org 2024-03-04 8:18 ` krebbel at gcc dot gnu.org 2024-03-04 16:31 ` segher at gcc dot gnu.org 2024-03-04 16:49 ` sarah.kriesch at opensuse dot org 2024-03-04 21:26 ` segher at gcc dot gnu.org 2024-03-05 7:31 ` krebbel at gcc dot gnu.org 2024-03-05 10:36 ` sarah.kriesch at opensuse dot org 2024-03-06 22:49 ` segher at gcc dot gnu.org 2024-03-06 22:53 ` segher at gcc dot gnu.org 2024-03-06 23:15 ` pinskia at gcc dot gnu.org 2024-03-07 9:26 ` krebbel at gcc dot gnu.org 2024-03-07 9:28 ` krebbel at gcc dot gnu.org 2024-03-07 9:34 ` krebbel at gcc dot gnu.org 2024-03-07 15:51 ` krebbel at gcc dot gnu.org [this message] 2024-03-07 15:52 ` krebbel at gcc dot gnu.org 2024-03-07 16:11 ` segher at gcc dot gnu.org 2024-03-07 16:19 ` segher at gcc dot gnu.org 2024-03-07 16:53 ` pinskia at gcc dot gnu.org 2024-03-07 16:57 ` pinskia at gcc dot gnu.org 2024-03-07 18:15 ` segher at gcc dot gnu.org 2024-03-07 19:42 ` segher at gcc dot gnu.org 2024-03-07 19:45 ` jakub at gcc dot gnu.org 2024-03-07 20:10 ` segher at gcc dot gnu.org 2024-03-07 20:17 ` krebbel at gcc dot gnu.org 2024-03-07 20:53 ` krebbel at gcc dot gnu.org 2024-03-20 11:53 ` [Bug target/101523] " rguenth at gcc dot gnu.org 2024-03-21 7:56 ` segher at gcc dot gnu.org 2024-03-21 8:15 ` rguenth at gcc dot gnu.org 2024-03-21 8:27 ` rguenth at gcc dot gnu.org 2024-03-21 12:57 ` segher at gcc dot gnu.org 2024-03-21 12:58 ` segher at gcc dot gnu.org 2024-03-21 13:15 ` rguenth at gcc dot gnu.org 2024-03-21 13:22 ` rguenth at gcc dot gnu.org 2024-03-22 8:07 ` rguenth at gcc dot gnu.org 2024-03-22 9:41 ` rguenth at gcc dot gnu.org 2024-03-22 9:42 ` sjames at gcc dot gnu.org 2024-03-22 9:42 ` sjames at gcc dot gnu.org 2024-03-22 9:52 ` rguenth at gcc dot gnu.org 2024-03-22 12:17 ` rguenth at gcc dot gnu.org 2024-03-22 12:38 ` rguenth at gcc dot gnu.org 2024-03-27 14:35 ` sarah.kriesch at opensuse dot org 2024-03-27 16:10 ` [Bug rtl-optimization/101523] " cvs-commit at gcc dot gnu.org 2024-03-27 16:53 ` segher at gcc dot gnu.org 2024-03-27 16:55 ` segher at gcc dot gnu.org 2024-04-03 10:58 ` rguenth at gcc dot gnu.org 2024-04-05 11:48 ` segher at gcc dot gnu.org 2024-04-05 12:20 ` rguenth at gcc dot gnu.org 2024-04-10 6:02 ` rguenth at gcc dot gnu.org 2024-04-10 15:51 ` segher at gcc dot gnu.org 2024-04-10 15:57 ` jakub at gcc dot gnu.org 2024-04-10 17:03 ` rguenth at gcc dot gnu.org 2024-04-10 17:45 ` sarah.kriesch at opensuse dot org 2024-05-04 6:00 ` segher at gcc dot gnu.org 2024-05-04 13:14 ` sarah.kriesch at opensuse dot org 2024-05-04 17:30 ` segher at gcc dot gnu.org 2024-05-06 9:21 ` rguenther at suse dot de 2024-05-06 9:40 ` segher at kernel dot crashing.org 2024-05-06 9:42 ` segher at gcc dot gnu.org 2024-05-06 9:46 ` 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-101523-4-Apk96rzAZi@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).