Explore >> Select a destination
|
You are here 
|
mcyoung.xyz | ||
| | | | |
etherealwake.com
|
|
| | | | | When writing a freestanding application, it's generally necessary for the firmware engineer to handle runtime initialization. Even when a library like newlib includes a rudimentary implementation of crt0.o, initialization is a very application-specific process owing to the need to initialize hardware, memory, and other loading tasks. In this essay, we examine the current and historical implementation of executable initialization, finishing with a minimal implementation usable with firmware applications. Note: Most firmware applications need to address the initialization of .data and .bss from nonvolatile memory. That is not addressed in this essay. | |
| | | | |
maskray.me
|
|
| | | | | Updated in 2024-04 (??????LLVM 2000 commits???) Compiler driver options Before describing the linker options, let's introduce the concept of driver options. The user-facing options of gcc and clang ar | |
| | | | |
blog.thea.codes
|
|
| | | | | A deep look into the black magic that is linker scripts. | |
| | | | |
nts.strzibny.name
|
|
| | | Here's one way of a cloud-independent deployment of Rails, Sidekiq, PostgreSQL, and Redis on single virtual server with Kamal. | ||
