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] Lots of else ifs take forever to compile
Date: Thu, 23 Dec 2004 01:43:00 -0000 [thread overview]
Message-ID: <20041223014337.19425.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-23 01:43 -------
This looks like a problem with the hash function for a REG when we
have many implicit sets:
Found 6001 implicit sets
SET hash table (6001 buckets, 6001 entries)
Index 0 (hash value 58)
(set (reg/v:SI 58 [ b ])
(const_int 1 [0x1]))
Index 1 (hash value 58)
(set (reg/v:SI 58 [ b ])
(const_int 10000 [0x2710]))
Index 2 (hash value 58)
(set (reg/v:SI 58 [ b ])
(const_int 10001 [0x2711]))
Index 3 (hash value 58)
(set (reg/v:SI 58 [ b ])
(const_int 10002 [0x2712]))
Index 4 (hash value 58)
(set (reg/v:SI 58 [ b ])
(const_int 10003 [0x2713]))
Index 5 (hash value 58)
(set (reg/v:SI 58 [ b ])
(const_int 10004 [0x2714]))
Index 6 (hash value 58)
(set (reg/v:SI 58 [ b ])
(const_int 10005 [0x2715]))
Index 7 (hash value 58)
(set (reg/v:SI 58 [ b ])
(const_int 10006 [0x2716]))
Index 8 (hash value 58)
(set (reg/v:SI 58 [ b ])
(const_int 10007 [0x2717]))
Index 9 (hash value 58)
(set (reg/v:SI 58 [ b ])
(const_int 10008 [0x2718]))
Index 10 (hash value 58)
(set (reg/v:SI 58 [ b ])
(const_int 10009 [0x2719]))
(etc.)
Needless to say, this results in truely dramatically bad compile
time behavior of the hash table.
--
What |Removed |Added
----------------------------------------------------------------------------
CC| |roger at eyesopen dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19097
next prev parent reply other threads:[~2004-12-23 1:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-21 1:57 [Bug rtl-optimization/19097] New: " 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 [this message]
2004-12-24 1:00 ` [Bug rtl-optimization/19097] [3.4/4.0 regression] Quadratic behavior with many sets for the same register in gcse CPROP steven at gcc dot gnu dot org
2004-12-28 18:48 ` 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=20041223014337.19425.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: 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).