[Openmcl-devel] M1 port: Call for funding
Tim McNerney
mc at media.mit.edu
Mon Jan 1 05:50:43 PST 2024
Yes! I would enthusiastically attend a “just bump the fasl version number” (i.e. null upgrade) bootstrapping class.
Modifying gdb so that it recognizes Lisp objects could help quite a bit (e.g. headers, type bits, etc). When I was at Harlequin, I modified gdb so it better displayed Dylan stack frames (and hid internal ones), and that wasn’t such a heavy lift, even for someone who’d never hacked gdb before.
--Tim
> On Dec 31, 2023, at 17:03, Andrew Shalit <alms at clozure.com> wrote:
>
> I believe bumping the fasl version requires a new kernel and lisp heap. So making that one change would allow you to go through the steps of bootstrapping a new kernal and image without having to worry about debugging code.
>
>
>>> On Dec 31, 2023, at 2:38 PM, Ron Garret <ron at flownet.com> wrote:
>>>
>>>
>>>> On Dec 31, 2023, at 11:23 AM, Andrew Shalit <alms at clozure.com> wrote:
>>>
>>> I’d suggest a first valuable step would be for people to learn how to bootstrap a new version of CCL.
>>
>> That sounds like a great idea. Probably the best way to do that would be to go to the git repo and find the last time a change was made that required this bootstrapping process. Does anyone happen to recall when that was? Even better, does anyone know how to find the actual commit(s)?
>>
>> rg
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clozure.com/pipermail/openmcl-devel/attachments/20240101/48c8c7b9/attachment.htm>
More information about the Openmcl-devel
mailing list