public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zadeck at naturalbridge dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/35065] [4.3 Regression] infinite loop while compiling VLC media player in vt_find_locations
Date: Tue, 12 Feb 2008 14:57:00 -0000	[thread overview]
Message-ID: <20080212145633.13161.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35065-5724@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from zadeck at naturalbridge dot com  2008-02-12 14:56 -------
Richi,

I looked at this code once but I really do not know this code at all and really
do not want to learn it.  It will take a fair amount of time to try to figure
out what the underlying dataflow problem is and then figure out how to modify
it so that it is strictly monotonic (i.e. guaranteed to converge).

However, given that this is just improving debugging information, it should be
possible to just hack a count of the number of iterations and just stop after
20, i.e the way that flow used to do it.  

If this is a blocker, this is what I would do to get the release out of the
door.  

Kenny


-- 


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


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

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-03 14:10 [Bug regression/35065] New: [4.3 regression] debian-gcc at lists dot debian dot org
2008-02-03 14:11 ` [Bug regression/35065] [4.3 regression] infinite loop while compiling VLC media player debian-gcc at lists dot debian dot org
2008-02-03 15:16 ` [Bug middle-end/35065] [4.3 Regression] " rguenth at gcc dot gnu dot org
2008-02-03 17:43 ` rguenth at gcc dot gnu dot org
2008-02-03 17:45 ` [Bug middle-end/35065] [4.3 Regression] infinite loop while compiling VLC media player in vt_find_locations rguenth at gcc dot gnu dot org
2008-02-04 22:52 ` [Bug debug/35065] " rguenth at gcc dot gnu dot org
2008-02-12 14:57 ` zadeck at naturalbridge dot com [this message]
2008-02-12 15:04 ` rguenther at suse dot de
2008-02-12 15:37 ` matz at gcc dot gnu dot org
2008-02-12 16:07 ` matz at gcc dot gnu dot org
2008-02-13 14:55 ` matz at gcc dot gnu dot org
2008-02-13 15:01 ` matz at gcc dot gnu dot org
2008-02-13 16:01 ` dominiq at lps dot ens dot fr
2008-02-13 16:18 ` matz at gcc dot gnu dot org
2008-02-13 22:24 ` jakub at gcc dot gnu dot org
2008-02-13 23:04 ` matz 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=20080212145633.13161.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).