|
You are here |
www.catch22.net | ||
| | | | |
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. | |
| | | | |
www.lukas-barth.net
|
|
| | | | | This article explores how to exploit side effects during dynamic initialization. It gives an overview over how dynamic initialization works in a typical C++ executable on Linux. | |
| | | | |
www.benshoof.org
|
|
| | | | | [AI summary] The author details the development of Minicrt, an updated version of the Libctiny C run-time library, to compile tiny Visual Studio programs, explaining compatibility features and workarounds for linker errors. | |
| | | | |
fossheim.io
|
|
| | | Data visualizations can be great to communicate complex data in an easy way. Unfortunately, there's a lot that can go wrong when it comes to accessibility. So I decided to start writing my own series about it. | ||