mysterymath

7 ms·

1.
by mysterymath 6mo ago
Beeeecause this was a lecture delivered at a Catholic philosophy/theology conference?
2.
by mysterymath 6mo ago
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 $.age and it.age, in
3.
by mysterymath 7mo ago
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 other, while I provided overall direction for the project. It
4.
by mysterymath 7mo ago
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 out by hand. But I definitely can't do that, and e
5.
Show HN: RISCY-V02: A 16-bit 2-cycle RISC-V-ish CPU in the 6502 footprint(github.com)
7 points by mysterymath 7mo ago|4 comments
6.
by mysterymath 10mo ago
Lol? https://github.com/mysterymath/llvm-mos/tree/regalloc
7.
by mysterymath 10mo ago
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 thing in the name of generality, but the way it s
8.
by mysterymath 1y ago
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 that wasn't part of ROM was an unusual novelty.
9.
by mysterymath 2y ago
Ah thanks, that's what I was looking for.
10.
by mysterymath 2y ago
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 the notice page is also "Website Title&q
11.
by mysterymath 2y ago
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 not necessarily even a
12.
by mysterymath 2y ago
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 legacy computing platform, and having a Unicode assi
13.
by mysterymath 2y ago
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 directly encode special characters for these c
14.
by mysterymath 2y ago
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" today, but they absolutely w
15.
by mysterymath 2y ago
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 translation of those semantics to LLVM IR targeting OS sysca
16.
by mysterymath 2y ago
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 structure; prose flows from one point to
17.
by mysterymath 2y ago
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 authority and assessing the world on their own we were more lik
18.
by mysterymath 2y ago
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 lines of constant distance along slooped floor surf
19.
by mysterymath 3y ago
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 they behaved, depending on an unfortunately ambiguous phra
20.
by mysterymath 3y ago
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-compliance is the lack of floating point support, whic
21.
by mysterymath 3y ago
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 of though; it's just difficult code
22.
by mysterymath 4y ago
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 priority allocator with nice live-range splitting. It
23.
by mysterymath 4y ago
https://llvm-mos.org/wiki/Rust
24.
by mysterymath 4y ago
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 tooling and techniques to a
25.
by mysterymath 4y ago
Que? We don't compile to a virtual machine, we compile to plain 6502 assembly. We do use 32 bytes of the zero page as a de-facto register file, but that's not at all uncommon in hand-written assembly either, it's just usually
26.
by mysterymath 4y ago
This has come up off and on, and it's looking increasingly unlikely. I've had to do some nasty surgery to the loop strength reduction pass, and I haven't yet found a way to generalize it. Still, I'm not ruling it out, it
27.
by mysterymath 4y ago
The AtariAge results are fairly out-of-date; I think that's even before we started doing whole-program zero-page allocation. The only real 6502-specific C caveat left for llvm-mos is that you should strongly prefer structs of arrays t
28.
EuroLLVM 2022: LLVM-MOS 6502 Back end: Having a Blast in the Past [video](youtube.com)
5 points by mysterymath 4y ago|1 comments
29.
by mysterymath 4y ago
Wiki: https://llvm-mos.org GitHub: https://github.com/llvm-mos/llvm-mos-sdk Slides: https://llvm.org/devmtg/2022-05/slides/2022EuroLLVM-LLVM-MOS...
30.
by mysterymath 4y ago
https://github.com/mrk-its/rust-mos

More ›