From: Matt Wette <matt.wette@gmail.com>
To: 38486@debbugs.gnu.org
Subject: bug#38486: hang
Date: Sat, 21 Mar 2020 14:42:23 -0700 [thread overview]
Message-ID: <a732488b-9e59-2d8d-27f8-04c45ae7870d@gmail.com> (raw)
In-Reply-To: <460c32b1-966a-079d-4187-de63f93c6e5f@gmail.com>
So I hacked modules/cps/optimize.scm to display the optimization phases.
Here is what I got up to the point where guile hangs.
It looks like it's hanging in specialize-numbers.
running eliminate-dead-code
running prune-top-level-scopes
running simplify
running contify
running inline-constructors
running elide-values
running prune-bailouts
running peel-loops
running eliminate-common-subexpressions
running type-fold
running resolve-self-references
running eliminate-dead-code
running simplify
running specialize-numbers
The patch:
--- module/language/cps/optimize.scm-orig 2020-03-21
14:16:17.313452995 -0700
+++ module/language/cps/optimize.scm 2020-03-21 14:18:32.264770889 -0700
@@ -73,7 +73,10 @@
(maybe-verify program)
(set! program
(if (kw-arg-ref opts kw default)
- (maybe-verify (pass program))
+ (begin
+ (display "running ") (display (quote pass)) (newline)
+ (force-output (current-output-port))
+ (maybe-verify (pass program)))
program))
...
(maybe-verify program)))
next prev parent reply other threads:[~2020-03-21 21:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 4:58 bug#38486: Compiler does not terminate Zack Marvel
2019-12-04 8:43 ` tomas
2020-03-21 20:32 ` bug#38486: compile livelock Matt Wette
2020-03-21 20:57 ` bug#38486: try all options Matt Wette
2020-03-21 21:42 ` Matt Wette [this message]
2020-03-22 2:43 ` bug#38486: specialize-numbers.scm: compute-significant-bits Matt Wette
2020-03-23 16:08 ` bug#38486: done Matt Wette
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a732488b-9e59-2d8d-27f8-04c45ae7870d@gmail.com \
--to=matt.wette@gmail.com \
--cc=38486@debbugs.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).