From: Andrea Corallo <acorallo@gnu.org>
To: Andrea Corallo <akrl@sdf.org>
Cc: "Lars Tveito" <larstvei@ifi.uio.no>, hokomo <hokomo@disroot.org>,
69872-done@debbugs.gnu.org,
"Gerd Möllmann" <gerd.moellmann@gmail.com>,
57957@debbugs.gnu.org,
"Stefan Monnier" <monnier@iro.umontreal.ca>,
"Lars Ingebrigtsen" <larsi@gnus.org>
Subject: bug#57957: bug#69872: 29.2; Async native compilation of seq.el test uses up resources and hangs
Date: Mon, 01 Apr 2024 16:46:47 -0400 [thread overview]
Message-ID: <yp1frw4oloo.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <yp1v85brhtv.fsf_-_@fencepost.gnu.org> (Andrea Corallo's message of "Sun, 24 Mar 2024 07:26:52 -0400")
Andrea Corallo <acorallo@gnu.org> writes:
> Andrea Corallo <akrl@sdf.org> writes:
>
>> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>
>>>> The question is of course also how much effort circular lists deserve in
>>>> the compiler. From my point of view, not too much because they aren't
>>>> very useful, in code at least. And dealing with them costs runtime.
>>>
>>> Circular data structures are perfectly normal in source code under
>>> a `quote` but the code itself should never be cyclic (so I think it
>>> would be OK to signal an error (and/or to inf-loop) when asked to
>>> compile a chunk of code that has a cycle). So we *should* handle
>>> circular data structures correctly.
>>
>> I agree, Saturday I should have some time to look into this.
>
> A little time after... I finally managed to get to it, sorry for the
> delay.
>
> I've pushed into master c5de73a95a6, it fixes my reprodurer here and
> adds a test for this.
>
> If anyone could confirm this is fixed i'll be (extremely) happy to close
> this :)
>
> Thanks
>
> Andrea
Right I'm closing this as I believe it's fixed, happy to re-open if it's
not the case.
Thanks!
Andrea
next prev parent reply other threads:[~2024-04-01 20:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 7:55 bug#57957: 29.0.50; Native compilation hangs on cyclic lists Lars Tveito
2022-09-20 15:33 ` Lars Ingebrigtsen
2022-09-21 19:18 ` Andrea Corallo
2022-09-22 11:15 ` Lars Ingebrigtsen
2022-09-22 12:06 ` Gerd Möllmann
2022-09-22 16:07 ` Andrea Corallo
2022-09-22 16:41 ` Gerd Möllmann
2022-09-22 17:10 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-22 22:39 ` Andrea Corallo
2024-03-24 11:26 ` bug#57957: bug#69872: 29.2; Async native compilation of seq.el test uses up resources and hangs Andrea Corallo
2024-04-01 20:46 ` Andrea Corallo [this message]
2022-09-25 10:02 ` bug#57957: 29.0.50; Native compilation hangs on cyclic lists Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-22 14:25 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=yp1frw4oloo.fsf@fencepost.gnu.org \
--to=acorallo@gnu.org \
--cc=57957@debbugs.gnu.org \
--cc=69872-done@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=gerd.moellmann@gmail.com \
--cc=hokomo@disroot.org \
--cc=larsi@gnus.org \
--cc=larstvei@ifi.uio.no \
--cc=monnier@iro.umontreal.ca \
/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).