public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/19097] [3.4/4.0 regression] Quadratic behavior with many sets for the same register in gcse CPROP Date: Fri, 24 Dec 2004 01:00:00 -0000 [thread overview] Message-ID: <20041224010044.11183.qmail@sourceware.org> (raw) In-Reply-To: <20041221015654.19097.phython@gcc.gnu.org> ------- Additional Comments From steven at gcc dot gnu dot org 2004-12-24 01:00 ------- We did not have implicit sets in 3.3, so it doesn't show this behavior. On the other hand, someone could feed RTL to 3.3 where a single register is set many times, and I'm sure it will show the same behavior. But in this case, with implicit sets, we could have it for normal code too, for example an implicit set from a switch condition. So I'm marking this as a regression from the last release without implicit sets. The memory issue is different, I'm not sure if/where/why we allocate too much. It's probably just bad cache behavior that makes this a "memory-hog": walk a very long linked list that doesn't fit in RAM, well, that sends any machine to swapping hell. I'm not seeing memory consumption grow in a non linear way, so I'm removing that keyword. -- What |Removed |Added ---------------------------------------------------------------------------- Keywords|memory-hog | Known to fail| |4.0.0 Known to work| |3.3.4 Last reconfirmed|2004-12-21 08:38:15 |2004-12-24 01:00:42 date| | Summary|Lots of else ifs take |[3.4/4.0 regression] |forever to compile |Quadratic behavior with many | |sets for the same register | |in gcse CPROP http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19097
next prev parent reply other threads:[~2004-12-24 1:00 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-12-21 1:57 [Bug rtl-optimization/19097] New: Lots of else ifs take forever to compile phython at gcc dot gnu dot org 2004-12-21 2:39 ` [Bug rtl-optimization/19097] " pinskia at gcc dot gnu dot org 2004-12-21 8:38 ` steven at gcc dot gnu dot org 2004-12-21 8:47 ` steven at gcc dot gnu dot org 2004-12-23 1:43 ` steven at gcc dot gnu dot org 2004-12-24 1:00 ` steven at gcc dot gnu dot org [this message] 2004-12-28 18:48 ` [Bug rtl-optimization/19097] [3.4/4.0 regression] Quadratic behavior with many sets for the same register in gcse CPROP bonzini at gcc dot gnu dot org 2005-03-05 19:53 ` [Bug rtl-optimization/19097] [3.4/4.0/4.1 " pinskia at gcc dot gnu dot org 2005-03-05 23:37 ` steven at gcc dot gnu dot org 2005-06-08 3:32 ` phython at gcc dot gnu dot org 2005-06-08 9:38 ` steven at gcc dot gnu dot org 2005-06-08 12:44 ` phython at gcc dot gnu dot org 2005-08-23 7:29 ` phython at gcc dot gnu dot org 2005-08-25 5:44 ` phython at gcc dot gnu dot org 2005-08-25 6:40 ` phython at gcc dot gnu dot org 2005-08-25 7:06 ` phython at gcc dot gnu dot org 2005-09-19 0:14 ` pinskia at gcc dot gnu dot org 2005-09-19 0:15 ` steven at gcc dot gnu dot org 2005-09-30 14:43 ` amacleod at redhat dot com
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=20041224010044.11183.qmail@sourceware.org \ --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).