From: Andy Wingo <wingo@pobox.com>
To: Julian Graham <joolean@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Possible infinite loop during compilation in 2.2
Date: Fri, 18 Apr 2014 21:20:05 +0200 [thread overview]
Message-ID: <87vbu6o36i.fsf@pobox.com> (raw)
In-Reply-To: <CANdC_RCpVru4G=B2QYjL_FxsQJfUVGFG_G5JLLOUG3W0SsabcQ@mail.gmail.com> (Julian Graham's message of "Fri, 18 Apr 2014 12:05:54 -0400")
On Fri 18 Apr 2014 18:05, Julian Graham <joolean@gmail.com> writes:
> I was experimenting with building one of my projects using Guile 2.2
> and found that some files just don't seem to want to finish compiling,
> and peg my CPU at 100% -- seems like they might be getting stuck in a
> loop. (Other files compile just fine.)
Interestingly this seems to happen at macro-expansion time. Did you C-c
your file early, or was this after letting it run for a while?
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2014-04-18 19:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-18 16:05 Possible infinite loop during compilation in 2.2 Julian Graham
2014-04-18 19:20 ` Andy Wingo [this message]
2014-04-18 19:21 ` Julian Graham
2014-04-18 19:57 ` Julian Graham
2014-04-18 21:43 ` Mark H Weaver
2014-04-18 22:28 ` Julian Graham
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=87vbu6o36i.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=joolean@gmail.com \
/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).