Viewing profile — mysterymath

Beeeecause this was a lecture delivered at a Catholic philosophy/theology conference?

Another point of view: ideally it would just be "Age". But in languages that don't have the ability to "open" scopes, one might be satisfied p.Age, being "the age". I've also seen …

TT will either make me a chip I can run, a chip I can run with some workarounds, or garbage. Only time will tell! As for Claude, honestly, as a partner. We bounced ideas off each o…

To me, it's plausible one might be able to make a similarly small RISCY-V02 on a 70s Rubylith NMOS process with dynamic logic, using pass transistors and tristate busses, all laid …

Finally finished my little CPU project, RISCY-V02. I built it (with Claude) to challenge the notion that the 6502 was a "local optimum" in its transistor budget. Given the constrai…

Lol? https://github.com/mysterymath/llvm-mos/tree/regalloc

Hey, llvm-mos maintainer here. I actually work on LLVM in my dayjob too, and I don't particularly want llvm-mos upstream. It stretches LLVM's assumptions a lot, which is a good thi…

You're talking about different 80s. On workstations and Unix mainframes, beasts like Smalltalk and Objective C roamed the Earth. On home computers, a resident relocatable driver th…

Ah thanks, that's what I was looking for.

There's something very hinky about this post. It links to efabless.com/notice, not efabless.com direcly, and there's no information about this on efabless.com proper. The title of …

See https://discourse.llvm.org/t/rfc-enabling-fexec-charset-supp... There's a lot of discussion about this; practically changing the execution character set isn't trivial, and it's…

This wouldn't have worked for the llvm-mos use case I mentioned; the actual identity is the useful part. I'd expect each of these symbols was associated with a numeric code on a le…

I'm definitely supportive of the original "Symbols for Legacy Computers" effort. We've been able to make great use of it in the llvm-mos toolchain for legacy systems; we can direct…

There's an old saying: "Yesterday's AI is today's algorithm". Few would consider A* search for route-planning or Alpha-Beta pruning for game playing to be "Capital A Captial I" tod…

Meh. Rust's safety guarantees typically depend on: - Soundness of their semantics at a conceptual level - Correct implementation of the semantics in rustc (in Rust) - Correct trans…

This is a bit tough I'm afraid; while I'm very appreciative of the effort, I don't actually like the parts of the series that I've read very much. The overall complaint is one of s…

I was just such a person. I was taught that being a YEC meant that we were the only ones who earnestly sought after the truth. The world was blind, and by rejecting a corrupted aut…

Duke3D isn't a raycaster; it's a portal-based quad rasterizer. Wall quads are forced vertical, and floor quads are rasterized using a neat trick. The renderer computes successive l…

The story is a little more complex than that; the semantics were internally consistent, but foot-gun-ey, and they could technically be taken to match GCC's documentation of how the…

Yep, llvm-mos-sdk is explicitly freestanding; the libc functions in the SDK follow the hosted C standard, but they don't add up to a hosted implementation. The only known C99 non-c…

I'd actually like the llvm-mos to do an automated AoS to SoA analysis and rewrite, but haven't gotten around to it yet. There aren't any intrinsic theoretical obstacles I'm aware o…

In LLVM-MOS, we mainly struggle with its register allocator; the rest of the backend is really quite reasonable. The "Greedy register allocator" in LLVM is a just finely tuned prio…

https://llvm-mos.org/wiki/Rust

I maintain a LLVM backend for the 6502: https://godbolt.org/z/6EWEb6c5E , https://llvm-mos.org I love compilers, and I work on LLVM full time at my day job. I love bringing modern …