another stupid pivot. turns out llvm is way harder to work with than i thought it was, so i might as well just write everything in c. no more originality!!
Reposted by
@penelopoison
i switched my site over to server-side includes, just making it easier for me to add new pages for new chapters of my scanlation projects
Ship
i switched my site over to server-side includes, just making it easier for me to add new pages for new chapters of my scanlation projects
i’ve pivoted.
modern piezoelectric speakers in keeping with the tradition of this general social malaise are probably 10 times worse and less flexible than the ibm 5150. i have no patience for rebooting or qemu so i thought why not use dos? and so i embarked on this terrifying journey…
pipeline:
- rust → llvm bitcode (cargo targeting x86_64, but as long as no cpu-specific instructions are used it should be fine)
- llvm bitcode → c (using rellic, which seems to be the cleanest)
- manually cleaning c, which can be easily automated
- c → x86 (watcom)
requirements for the rust code:
- no_std
- no panic!ing
- no cpu-specific instructions
- write your own bindings to watcom c headers (if you need them) since clang doesn’t understand watcom jank
soon all will be automated. then i can continue on my quest to oxidize bad apple on the 5150
pc speaker stuff! i’m working on the resampling and frequency calculations portions now, hopefully the scheduler will play nicer with me…
