From: Andrea Corallo <acorallo@gnu.org>
To: Hugh Daschbach <hdasch@ccss.com>
Cc: 75135@debbugs.gnu.org
Subject: bug#75135: 30.0.93; Infinite loop in comp--native-compile
Date: Sun, 29 Dec 2024 05:17:10 -0500 [thread overview]
Message-ID: <yp1wmfi7pzt.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87msgiasma.fsf@klaatu.mail-host-address-is-not-set> (Hugh Daschbach's message of "Thu, 26 Dec 2024 16:15:25 -0800")
Hugh Daschbach <hdasch@ccss.com> writes:
> Emacs hangs when attempting to compile tests from obsolete ELPA package
> seq.
>
> To reproduce:
>
> ```
> curl -o /tmp/seq-tests.el https://git.savannah.gnu.org/cgit/emacs/elpa.git/plain/tests/seq-tests.el?h=externals/seq
> $ emacs -Q --eval "(progn (setq debug-on-quit t) (require 'comp) (comp--native-compile \"/tmp/seq-tests.el\" nil))"
> ```
>
> Press C-g shortly after the Emacs frame opens. This produces the
> following backtrace:
Okay I can reproduce on master as well.
> ```
> Debugger entered--Lisp error: (quit)
> #f(compiled-function (x) #<bytecode -0x145e3142cf39a7e4>)(1)
> cl--nsublis-rec((1 . #1))
> cl--nsublis-rec((#s(comp-mvar :typeset (t) :valset nil :range nil :neg nil :id 34397705172435 :slot 0) (1 . #3)))
> cl--nsublis-rec(((#s(comp-mvar :typeset (t) :valset nil :range nil :neg nil :id 34397705172435 :slot 0) (1 . #4))))
> cl-nsublis(((nil . #s(comp-mvar :typeset (t) :valset nil :range nil :neg nil :id 34397705043564 :slot 1))) (#s(comp-mvar :typeset (t) :valset nil :range nil :neg nil :id 34397705172435 :slot 0) (1 . #4)) :if #f(compiled-function (x) #<bytecode -0x145e3142cf39a7e4>))
> cl-nsubst-if(#s(comp-mvar :typeset (t) :valset nil :range nil :neg nil :id 34397705043564 :slot 1) #f(compiled-function (x) #<bytecode -0x145e3142cf39a7e4>) (#s(comp-mvar :typeset (t) :valset nil :range nil :neg nil :id 34397705172435 :slot 0) (1 . #5)))
> comp--ssa-rename-insn((setimm #s(comp-mvar :typeset (t) :valset nil :range nil :neg nil :id 34397705172435 :slot 0) (1 . #4)) #s(comp-vec :data #<hash-table eql 5/6 0x1f48d6ffbc9c ...> :beg 0 :end 5))
[...]
> comp--ssa()
> comp--fwprop(nil)
> comp--native-compile("/tmp/seq-tests.el" nil)
> (progn (setq debug-on-quit t) (require 'comp) (comp--native-compile "/tmp/seq-tests.el" nil))
> eval((progn (setq debug-on-quit t) (require 'comp) (comp--native-compile "/tmp/seq-tests.el" nil)) t)
> command-line-1(("--eval" "(progn (setq debug-on-quit t) (require 'comp) (comp--native-compile \"/tmp/seq-tests.el\" nil))"))
> command-line()
> normal-top-level()
> ```
>
> Admittedly, trying to compile an obsolete ELPA package is not a good
> idea. In fact, it was a configuration bug. But it might be interesting
> to see why the compiler hangs.
Yes it's certanly interesting thanks for the report will look at.
Andrea
next prev parent reply other threads:[~2024-12-29 10:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-27 0:15 bug#75135: 30.0.93; Infinite loop in comp--native-compile Hugh Daschbach
2024-12-29 10:17 ` Andrea Corallo [this message]
2024-12-29 14:23 ` Andrea Corallo
2024-12-29 14:28 ` Eli Zaretskii
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yp1wmfi7pzt.fsf@fencepost.gnu.org \
--to=acorallo@gnu.org \
--cc=75135@debbugs.gnu.org \
--cc=hdasch@ccss.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).