public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dberlin at dberlin dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/35204] [4.3 Regression] crash by too deep recursion in DFS tree-ssa-sccvn.c:1898
Date: Sat, 16 Feb 2008 14:57:00 -0000	[thread overview]
Message-ID: <20080216145631.30756.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35204-3760@http.gcc.gnu.org/bugzilla/>



------- Comment #20 from dberlin at gcc dot gnu dot org  2008-02-16 14:56 -------
Subject: Re:  [4.3 Regression] crash by too deep recursion in DFS
tree-ssa-sccvn.c:1898

So, there are better SCC algorithms.
In particular, Nuutilla's algorithm will avoid placing a bunch of
nodes on the stack (pearce's is a modification of this).
This is what structalias uses.

You can also certainly make the algorithm non-recursive, but it is a
bunch of work.

See http://www.cise.ufl.edu/research/sparse/btf/BTF/Source/btf_strongcomp.c
for an example of a non-recursive SCC finder.
In essence, you have to keep stacks for each variable.


On 16 Feb 2008 12:51:44 -0000, rguenth at gcc dot gnu dot org
<gcc-bugzilla@gcc.gnu.org> wrote:
>
>
> ------- Comment #19 from rguenth at gcc dot gnu dot org  2008-02-16 12:51 -------
> Note that while it definitely improves stack usage, the total memory usage is
> likely to go up (vectors allocate some extra heap, the iters are now
> addressable
> and thus consume full memory) and as the ssa_op_iter is now pinned to memory
> it is likely the algorithm is slower as well.
>
>
> --
>
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35204
>
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug, or are watching someone who is.
>


-- 


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


  parent reply	other threads:[~2008-02-16 14:57 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-14 23:13 [Bug middle-end/35204] New: " marcus at jet dot franken dot de
2008-02-14 23:14 ` [Bug middle-end/35204] " marcus at jet dot franken dot de
2008-02-14 23:16 ` marcus at jet dot franken dot de
2008-02-14 23:18 ` marcus at jet dot franken dot de
2008-02-14 23:21 ` marcus at jet dot franken dot de
2008-02-14 23:22 ` [Bug middle-end/35204] [4.3 Regression] " rguenth at gcc dot gnu dot org
2008-02-14 23:25 ` steven at gcc dot gnu dot org
2008-02-14 23:26 ` steven at gcc dot gnu dot org
2008-02-15  9:09 ` rguenther at suse dot de
2008-02-15 13:32 ` rguenth at gcc dot gnu dot org
2008-02-15 13:36 ` rguenth at gcc dot gnu dot org
2008-02-15 16:21 ` steven at gcc dot gnu dot org
2008-02-15 16:30 ` rguenth at gcc dot gnu dot org
2008-02-16  8:46 ` marcus at jet dot franken dot de
2008-02-16  9:34 ` steven at gcc dot gnu dot org
2008-02-16  9:40 ` steven at gcc dot gnu dot org
2008-02-16 10:41 ` rguenth at gcc dot gnu dot org
2008-02-16 11:24 ` rguenth at gcc dot gnu dot org
2008-02-16 12:12 ` rguenth at gcc dot gnu dot org
2008-02-16 12:49 ` rguenth at gcc dot gnu dot org
2008-02-16 12:52 ` rguenth at gcc dot gnu dot org
2008-02-16 14:57 ` dberlin at dberlin dot org [this message]
2008-02-16 15:23 ` rguenth at gcc dot gnu dot org
2008-02-17 16:25 ` rguenth at gcc dot gnu dot org
2008-03-14 17:11 ` [Bug middle-end/35204] [4.3/4.4 " rguenth at gcc dot gnu dot org
2008-04-03  9:54 ` rguenth at gcc dot gnu dot org
2008-04-03 10:03 ` rguenth at gcc dot gnu dot org
2008-05-20 16:33 ` jakub at gcc dot gnu dot org
2008-05-20 18:29 ` rguenth at gcc dot gnu dot org
2008-05-20 20:41 ` rguenth at gcc dot gnu dot org
2008-05-20 20:58 ` rguenth at gcc dot gnu dot org
2008-05-20 20:59 ` rguenth at gcc dot gnu dot org
2008-07-11 11:01 ` marion dot deveaud at siemens 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=20080216145631.30756.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).