poplaay.blogg.se

1. Hack run zero vs hack run how to#
2. Hack run zero vs hack run Patch#
3. Hack run zero vs hack run software#

Hack run zero vs hack run software#

Occasionally something from their past reappears, like the QuickDraw GX font format from the 90s that became the basis for today’s variable fonts on the web.Īpple has always been fine with some software not making the leap to the next operating system or processor architecture. Sure, they could have kept Carbon around or pick your favorite framework from the past but that’s generally not their thing. Reasonable people can disagree but Apple is about the present and the future, not the past. They’re not like Microsoft which keeps legacy technologies around for backwards compatibility for several years after a technology is no longer mainstream. (And they didn't want Intel computers to be able to run anything their new Apple Silicon computers could not.) And, sooner or later, they’re going to have to make these changes: OpenBSD already enforces W^X (but provides a workaround), and MIT/GNU Scheme already applies a paxctl workaround to gain W|X on NetBSD.īut actually, I personally believe that the actual reason Apple killed 32bit support was because they didn't want to build it into Rosetta. Some of the necessary changes are already sketched out in cmpint.txt. They already call an I-cache flush function after each modification, so this shouldn’t be too bad.

Hack run zero vs hack run Patch#

to patch addresses after GC relocation), a system-specific hook function will need to be called to set the permissions to RW. The closure/function objects can be made to point to the code, or, if they don’t need to be written often, simply allocated wholly from the “code” pages. It can still be garbage collected and such - they will probably need to make a separate set of allocation functions for code vs. Compiled code needs to be allocated separately from Scheme objects. If you are still interested in getting the books going with MIT-Scheme, I put a decent amount of work into the exercises using the original codebase here, including a dockerized version of mit-scheme and the scmutils package that might be useful.įrom perusing the source of the MIT/GNU Scheme compiler, I suspect that “only” two changes are needed to support W^X: He responded saying he'll get back to me this afternoon, so I'll post here once I have details.

Hack run zero vs hack run how to#

I actually wrote to GJS this morning asking for instructions on how to compile the original "scmutils", since I have the same problem. (That will change, as I've been pushing bugfixes and performance improvements back upstream as I go, as a meager gift to GJS for making this huge, amazing library in the first place.) The Clojure port is quite fast, faster than the original for all benchmarks GJS has sent me, and more fleshed out. It is good enough! Almost all code forms from the book live in the tests (see the FDG directory, for example), and there are a few nice environments like Nextjournal where everything from the books works in the browser.