public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "danglin at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/31944] Endless loop while building a 64-bit 2.6.20 kernel
Date: Sun, 20 May 2007 18:02:00 -0000	[thread overview]
Message-ID: <20070520180226.2740.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31944-8932@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from danglin at gcc dot gnu dot org  2007-05-20 19:02 -------
In order to prevent flush_hash_table from looping forever, the call to
invalidate (p->exp, VOIDmode) has to remove the element p.  However, this
doesn't happen.  It only removes the entry if lookup_for_remove finds the
pseudo:

            /* Because a register can be referenced in more than one mode,
               we might have to remove more than one table entry.  */
            struct table_elt *elt;

            while ((elt = lookup_for_remove (x, hash, GET_MODE (x))))
              remove_from_table (elt, hash);

For some reason, reg:DI 66 isn't found:

(gdb) p lookup_for_remove (0x800003fffec89d00, 29, DImode)
$20 = (struct table_elt *) 0x0

I'm thinking that flush_hash_table should check p after calling invalidate
and call remove_from_table if it's nonzero.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31944


  parent reply	other threads:[~2007-05-20 18:02 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-15 23:14 [Bug c/31944] New: " aurelien at aurel32 dot net
2007-05-16 10:08 ` [Bug rtl-optimization/31944] " aurelien at aurel32 dot net
2007-05-17  2:55 ` danglin at gcc dot gnu dot org
2007-05-20 16:38 ` danglin at gcc dot gnu dot org
2007-05-20 17:15 ` danglin at gcc dot gnu dot org
2007-05-20 18:02 ` danglin at gcc dot gnu dot org [this message]
2007-05-20 20:31 ` danglin at gcc dot gnu dot org
2007-12-05 20:33 ` [Bug rtl-optimization/31944] [4.1/4.2/4.3 Regression] " danglin at gcc dot gnu dot org
2007-12-05 21:51 ` rguenth at gcc dot gnu dot org
2007-12-05 22:29 ` steven at gcc dot gnu dot org
2007-12-15 23:17 ` dave at hiauly1 dot hia dot nrc dot ca
2007-12-26  1:34 ` pinskia at gcc dot gnu dot org
2008-01-01  2:11 ` [Bug rtl-optimization/31944] [4.1/4.2 " danglin at gcc dot gnu dot org
2008-01-01 17:00 ` rguenther at suse dot de
2008-01-01 21:34 ` [Bug rtl-optimization/31944] [4.1/4.2/4.3 " danglin at gcc dot gnu dot org
2008-01-08 16:18 ` steven at gcc dot gnu dot org
2008-01-08 16:45 ` rguenth at gcc dot gnu dot org
2008-01-09 15:54 ` rguenth at gcc dot gnu dot org
2008-01-09 19:23 ` steven at gcc dot gnu dot org
2008-01-10  1:00 ` steven at gcc dot gnu dot org
2008-01-10 23:59 ` janis at gcc dot gnu dot org
2008-01-11  1:02 ` steven at gcc dot gnu dot org
2008-01-11  1:03 ` janis at gcc dot gnu dot org
2008-01-11  1:08 ` steven at gcc dot gnu dot org
2008-01-11  1:24 ` steven at gcc dot gnu dot org
2008-01-11 19:13 ` ebotcazou at gcc dot gnu dot org
2008-01-11 19:46 ` ebotcazou at gcc dot gnu dot org
2008-01-11 21:52 ` dave at hiauly1 dot hia dot nrc dot ca
2008-01-12  4:00 ` steven at gcc dot gnu dot org
2008-01-12  8:36 ` ebotcazou at gcc dot gnu dot org
2008-01-14 12:36 ` ebotcazou at gcc dot gnu dot org
2008-01-14 12:46 ` ebotcazou at gcc dot gnu dot org
2008-01-14 12:46 ` ebotcazou at gcc dot gnu dot org
2008-01-14 12:48 ` ebotcazou at gcc dot gnu dot 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=20070520180226.2740.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).