From: <tomas@tuxteam.de>
To: 38486@debbugs.gnu.org
Subject: bug#38486: Compiler does not terminate
Date: Wed, 4 Dec 2019 09:43:04 +0100 [thread overview]
Message-ID: <20191204084304.GB15855@tuxteam.de> (raw)
In-Reply-To: <460c32b1-966a-079d-4187-de63f93c6e5f@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 754 bytes --]
On Tue, Dec 03, 2019 at 09:58:00PM -0700, Zack Marvel wrote:
> Hello,
>
> When compiling the following program, the compiler does not terminate.
[...]
> I can produce this behavior with Guile 2.2.4 and 2.2.6. I'm running
> Debian 10 amd64, and I compiled Guile with GCC 8.3.0.
FWIW, I just tried with guile 2.9.5 and the compile terminates:
tomas@trotzki:~$ guile /tmp/zack.scm
;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0
;;; or pass the --no-auto-compile argument to disable.
;;; compiling /tmp/zack.scm
;;; compiled /home/tomas/.cache/guile/ccache/3.0-LE-8-4.1/tmp/zack.scm.go
(after having saved your file to /tmp/zack.scm, that is).
So another data point, I assume :-)
Cheers
-- t
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2019-12-04 8:43 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 [this message]
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 ` bug#38486: hang Matt Wette
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=20191204084304.GB15855@tuxteam.de \
--to=tomas@tuxteam.de \
--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).