2 comments

  • RodgerTheGreat5 hours ago
    It's always a delight to read about your projects, Oscar. Every program is a jewel.
  • initramfs5 hours ago
    how does a debug file output 8GB+? Is it running for minutes/hours? Or is it in a format that uses a lot of rich text? I would assume a text file in hex or unicode wouldn't use very much.. Is there a way to create intervals of log files so they have a cap on the size?
    • nanochess4 hours ago
      It is a simple debugger log in the transputer emulator (enabled by compilation option) which outputs each instruction executed so far, around 70 bytes per line displaying the 3 registers, the stack pointer, the instruction pointer, and the disassembled instruction.<p>The emulated C compiler processed a whole file ccvars.c before getting stuck in ccinter.c (this is the 5gb mark, approximately 78 millions of instructions executed). I stopped the process as soon as I saw it was stuck, but the emulator is fast, and I got extra 3 gb in the log. All this happened in less than two minutes.
      • vanderZwan3 hours ago
        Another reminder of how easy it is to forget how ridiculously fast computers are these days (especially when you&#x27;re like me and not writing stuff close to the metal for your day job).