about summary refs log tree commit diff stats
path: root/apps/raytracing/vec.mu
Commit message (Collapse)AuthorAgeFilesLines
* 7842 - new directory organizationKartik K. Agaram2021-03-031-135/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Baremetal is now the default build target and therefore has its sources at the top-level. Baremetal programs build using the phase-2 Mu toolchain that requires a Linux kernel. This phase-2 codebase which used to be at the top-level is now under the linux/ directory. Finally, the phase-2 toolchain, while self-hosting, has a way to bootstrap from a C implementation, which is now stored in linux/bootstrap. The bootstrap C implementation uses some literate programming tools that are now in linux/bootstrap/tools. So the whole thing has gotten inverted. Each directory should build one artifact and include the main sources (along with standard library). Tools used for building it are relegated to sub-directories, even though those tools are often useful in their own right, and have had lots of interesting programs written using them. A couple of things have gotten dropped in this process: - I had old ways to run on just a Linux kernel, or with a Soso kernel. No more. - I had some old tooling for running a single test at the cursor. I haven't used that lately. Maybe I'll bring it back one day. The reorg isn't done yet. Still to do: - redo documentation everywhere. All the README files, all other markdown, particularly vocabulary.md. - clean up how-to-run comments at the start of programs everywhere - rethink what to do with the html/ directory. Do we even want to keep supporting it? In spite of these shortcomings, all the scripts at the top-level, linux/ and linux/bootstrap are working. The names of the scripts also feel reasonable. This is a good milestone to take stock at.
* 7294Kartik Agaram2020-11-281-4/+4
|
* 7165Kartik Agaram2020-11-031-1/+1
| | | | | All tasks of https://github.com/akkartik/mu/issues/45#issuecomment-719990879 should now be complete.
* 7159 - explicitly use 'return' everywhereKartik Agaram2020-11-021-4/+6
| | | | https://github.com/akkartik/mu/issues/45#issuecomment-719990879, task 2.
* 6960Kartik Agaram2020-10-051-19/+103
|
* 6949 - snapshot of next raytracing milestoneKartik Agaram2020-10-041-14/+14
| | | | | | | | | | | | | Not yet right, but worth a snapshot just because it gives a cool result. Here, try it out: $ ./translate_mu_debug apps/raytracing/3.mu $ ./a.elf > x.ppm Now view x.ppm as an image. In general, this was quite tedious to write. And a still-open question is how to emit the progress bar to stderr. My options are to either duplicate all my print-* functions (already proliferating) or add global variables to Mu.
* 6948 - stress-testing prints of floatsKartik Agaram2020-10-041-0/+11
| | | | Looks good.
* 6940Kartik Agaram2020-10-031-10/+10
|
* 6935 - raytracing using floatsKartik Agaram2020-10-031-0/+38