public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Jan Hubicka <jh@suse.cz> To: hubicka@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: middle-end/6566: sparc64-unknown-netbsd-gcc loops consuming memory Date: Fri, 07 Jun 2002 04:26:00 -0000 [thread overview] Message-ID: <20020607112606.9705.qmail@sources.redhat.com> (raw) The following reply was made to PR middle-end/6566; it has been noted by GNATS. From: Jan Hubicka <jh@suse.cz> To: davem@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, hubicka@gcc.gnu.org, nobody@gcc.gnu.org, thorpej@wasabisystems.com, gcc-gnats@gcc.gnu.org Cc: Subject: Re: middle-end/6566: sparc64-unknown-netbsd-gcc loops consuming memory Date: Fri, 7 Jun 2002 13:22:22 +0200 > Synopsis: sparc64-unknown-netbsd-gcc loops consuming memory > > Responsible-Changed-From-To: unassigned->hubicka > Responsible-Changed-By: davem > Responsible-Changed-When: Fri Jun 7 01:32:16 2002 > Responsible-Changed-Why: > Jan can you take a look at this? The problem is > calculate_global_regs_live() is what is looping. > Every iteration, right before qhead gets to qtail > in the main loop, we advance qtail almost through > the whole queue. This process repeats forever. > Any target crossed to sparc64-netbsd will be able > to reproduce this so it should be easy for you to > work on it. > Thanks. > State-Changed-From-To: open->analyzed > State-Changed-By: davem > State-Changed-When: Fri Jun 7 01:32:16 2002 > State-Changed-Why: > calculate_global_regs_live loops forever never making > forward progress This has been discussed on the list briefly. The problem is that iterative dataflow is not guaranteed to terminate when the starting sollution is not strictly bellow the correct one. We commonly do that and situation got worse after the renumbering changes, but really it just makes latent bug to happen more often. I want to take a look at it today or tomorrow. My plan is to turn dataflow into hybrid search, as df.c does, so we save some bits and create extra bitmap for each basic block noting changes in the liveness. When we change liveness of given pseudo twice, we wipe all the liveness bits of it and re-start relaxation. Not perfect sollution, but should work in practice. I am still looking for hints in the literatue, but most of it does appear to suggest that inverval analysis is the proper way to go. Honza > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6566
next reply other threads:[~2002-06-07 11:26 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-06-07 4:26 Jan Hubicka [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-06 13:14 hubicka 2002-06-07 1:32 davem
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=20020607112606.9705.qmail@sources.redhat.com \ --to=jh@suse.cz \ --cc=gcc-prs@gcc.gnu.org \ --cc=hubicka@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).