Explore >> Select a destination
|
You are here 
|
werat.dev | ||
| | | | |
venam.net
|
|
| | | | | An executable is something that causes a computer to perform some tasks according to encoded instructions. It's in opposition to a data file which must be parsed by another program to be meaningful, for example an image or video. The instructions are usually in machine code, read by the cpu and so dependent on the cpu architecture. An ex... | |
| | | | |
shrik3.com
|
|
| | | | | Personal blog. | |
| | | | |
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. | |
| | | | |
jawher.me
|
|
| | | |||
