Explore >> Select a destination
|
You are here 
|
jk.ozlabs.org | ||
| | | | |
bellard.org
|
|
| | | | | [AI summary] The author describes the Obfuscated Tiny C Compiler (OTCC), a minimal self-hosting C compiler created for the IOCCC that generated portable i386 ELF executables from a 2048-byte source code limit. | |
| | | | |
www.bitsnbites.eu
|
|
| | | | | [AI summary] This article provides a quick introduction to developing software for the open-source MRISC32 32-bit RISC architecture using a GCC-based toolchain and a simulator, including examples from compiling C code and running DOOM. | |
| | | | |
squanderingti.me
|
|
| | | | | Exploring the innards of an ELF binary to find the physical location of main. | |
| | | | |
jmmv.dev
|
|
| | | In a recent work discussion, I came across an argument that didn't sound quite right. The claim was that we needed to set up containers in our developer machines in order to run tests against a modern glibc. The justifications were that using LD_LIBRARY_PATH to load a different glibc didn't work and statically linking glibc wasn't possible either. But... running a program against a version of glibc that's different from the one installed on the system seems like a pretty standard requirement, doesn't it?... | ||
