3 ms·

Two notes to the author: 1. It would be nice to explain how to install an assembler (part of gcc?), how to run it on source code, how to run the program. Googl

Two notes to the author: 1. It would be nice to explain how to install an assembler (part of gcc?), how to run it on source code, how to run the program. Googled, not tested: as -o prog.o prog.s ld -o prog prog.o ./prog 2. Apparently GitHub accepts commits in the future because the last ones in this repo are timestamped Dec 23 2023.

masklinn 4y ago
> Apparently GitHub accepts commits in the future Of course. And this is made very annoying by github also insisting on reordering commits “chronologically” rather than topologically. If someone fucks up their local date (because they wanted to test something and forgot to reset it) you get a commit permanently pinned at the top of a branch until that date passes.
ryao 4y ago
I am not the author, but I suspect qemu-user would be helpful here: https://www.qemu.org/docs/master/user/main.html https://www.qemu.org/docs/master/user/main.html He would just need to say how to get an assembler that would work. llvm-as might work, but I am not sure how to get it to produce code for another architecture offhand.
- ptspts 4y ago
  On my Ubuntu, there are many cross-assemblers (including ARM, RISC-V and PowerPC) and linkers available in packages. These packages have binutils in their name. Once installed, the assembler command has -as at the end of its name, and the linker has -ld there.
canis-fam 4y ago
Criticism appreciated. The main README now contains install and build instructions. The main body of the book will, over time, be updated to include build instructions for each example. As per date... I'm at a loss. I believe my own machines are set correctly.
Kwpolska 4y ago
Why would GitHub prevent commits from the future? Git allows commit dates from the future and from before git was invented, and GitHub's job is to store git repositories.
- pmontra 4y ago
  Locally git can't tell if the clock is in the future, unless it starts checking ntp servers or the like. However it's not its own business IMHO. As a collaboration tool GitHub might refuse timestamps too much in the future, at least as an optional setting of the repository. If a coworker inadvertently moves the clock forward by an year when looking for the day of next new year eve, then makes a day worth of commits and pushes them, we'll have to delete those commits and make them again with the correct date.

masklinn 4y ago

> Apparently GitHub accepts commits in the future Of course. And this is made very annoying by github also insisting on reordering commits “chronologically” rather than topologically. If someone fucks up their local date (because they wanted to test something and forgot to reset it) you get a commit permanently pinned at the top of a branch until that date passes.

ryao 4y ago

I am not the author, but I suspect qemu-user would be helpful here: https://www.qemu.org/docs/master/user/main.html https://www.qemu.org/docs/master/user/main.html He would just need to say how to get an assembler that would work. llvm-as might work, but I am not sure how to get it to produce code for another architecture offhand.

ptspts 4y ago
On my Ubuntu, there are many cross-assemblers (including ARM, RISC-V and PowerPC) and linkers available in packages. These packages have binutils in their name. Once installed, the assembler command has -as at the end of its name, and the linker has -ld there.

canis-fam 4y ago

Criticism appreciated. The main README now contains install and build instructions. The main body of the book will, over time, be updated to include build instructions for each example. As per date... I'm at a loss. I believe my own machines are set correctly.

Kwpolska 4y ago

Why would GitHub prevent commits from the future? Git allows commit dates from the future and from before git was invented, and GitHub's job is to store git repositories.

pmontra 4y ago
Locally git can't tell if the clock is in the future, unless it starts checking ntp servers or the like. However it's not its own business IMHO. As a collaboration tool GitHub might refuse timestamps too much in the future, at least as an optional setting of the repository. If a coworker inadvertently moves the clock forward by an year when looking for the day of next new year eve, then makes a day worth of commits and pushes them, we'll have to delete those commits and make them again with the correct date.