Elektrine
Log in Register

#compiler

13 posts · Last used 21d

Lexy 🦕 @lexplt@hachyderm.io
· 3w ago
macOS 27 Holden gate broke my #cpp compiler So I fixed it #macos #apple #compiler https://lexp.lt/posts/macos_golden_gate_cpp_compiler/
Lexy

macOS 27 causing C++ linker errors

macOS 27 Golden Gate has just been released, and I updated perhasp a bit too quickly. All I wanted was to see if I could still compile my C++ projects, and what needed to be changed to run on the new OS version.\nLinker error I’m now getting hit by a linker error, that will block CMake from configuring a project and building it:\n1 2 3 4 5 6 7 8 9

2
0
2
0
13 @13@2137.social
· 2mo ago
DOOM runs (slowly) in a IBM PC-Compatible CSS Sheet https://hackaday.com/2026/07/15/doom-runs-slowly-in-a-ibm-pc-compatible-css-sheet/ #Retrocomputing #Compiler #Css #Emulator #IBMPC #Keepingitweird
DOOM Runs (slowly) In A IBM PC-Compatible CSS Sheet
Hackaday

DOOM Runs (slowly) In A IBM PC-Compatible CSS Sheet

Just when you thought we’d run out of things to port DOOM to, here comes [Ahmed Amer] with his CSS-DOS, a massive 300 MB CSS style sheet, that runs not just DOS, but Windows 1.0 and, of cours…

0
0
0
0
Brian Swetland @swetland@chaos.social
· 5mo ago
Grr. I really should just do simple linear scan register allocation with the dumb pass-everything-on-the-stack ABI to start with, but I keep trying to map out how "do it right" with a more realistic pass-by-registers ABI, etc. The desire to solve the whole problem "for real" is fighting with the desire to get a basic implementation working first. Ideally I'd leave things in the argument registers as long as possible *and* avoid spilling to the stack around function calls... #Compiler #PLdev
0
1
0
0
You've seen all posts