all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Juri Linkov <juri@linkov.net>
Cc: Andy Moreton <andrewjmoreton@gmail.com>,
	Pip Cet <pipcet@gmail.com>,
	46906@debbugs.gnu.org
Subject: bug#46906: 28.0.50; byte compiler infloops trying to compile infloop
Date: Mon, 20 Jun 2022 02:00:57 +0200	[thread overview]
Message-ID: <878rpsryo6.fsf@gnus.org> (raw)
In-Reply-To: <87k0qlrb8z.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 05 Mar 2021 14:17:00 +0100")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> I don't think that would work -- our threading stuff is based on
> "cooperative multithreading", I think?  Which means that the code we're
> testing has to call `yield', which it normally doesn't.

(I'm going through old bug reports that unfortunately weren't resolved
at the time.)

We apparently forgot to apply Pip's fix because we started talking about
fixing the test harness.  So I've now applied the fix, but not the test,
because we don't really have a good way to test infinite loops in ert.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2022-06-20  0:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-03 21:14 bug#46906: 28.0.50; byte compiler infloops trying to compile infloop Pip Cet
2021-03-03 21:44 ` Pip Cet
2021-03-03 23:33   ` Andy Moreton
2021-03-04  7:17     ` Pip Cet
2021-03-04  9:15       ` Juri Linkov
2021-03-04 10:19         ` Pip Cet
2021-03-04 11:16           ` Lars Ingebrigtsen
2021-03-04 12:15             ` Pip Cet
2021-03-05 13:16               ` Lars Ingebrigtsen
2021-03-04 17:58           ` Juri Linkov
2021-03-04 18:50             ` Pip Cet
2021-03-05 13:17             ` Lars Ingebrigtsen
2022-06-20  0:00               ` Lars Ingebrigtsen [this message]

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=878rpsryo6.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=46906@debbugs.gnu.org \
    --cc=andrewjmoreton@gmail.com \
    --cc=juri@linkov.net \
    --cc=pipcet@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.