Using GCC's Nested Functions with Wide Pointers and No Trampolines II
uecker
92 points
45 comments
August 15, 2026
Related Discussions
Found 5 related stories in 257.7ms across 8,687 title embeddings via pgvector HNSW
- Indirect Calling of Nested Functions on GCC Without Executable Stack uecker · 72 pts · August 29, 2026 · 73% similar
- Getting silly with C, part and((int*)-8)[3] surprisetalk · 26 pts · August 21, 2026 · 55% similar
- Two ARM64-specific compiler optimization bugs, in GCC 15/16 and Rust, hit curl torutofu · 51 pts · October 06, 2026 · 52% similar
- Tumble Forth – from assembly to OS with C compiler (2023) vicek22 · 70 pts · August 21, 2026 · 50% similar
- Reducing undefined behavior in the C language chmaynard · 27 pts · September 28, 2026 · 50% similar
Discussion Highlights (3 comments)
mananaysiempre
What about your older patch where -fno-trampolines meant a function pointer could either be a code pointer or a closure (descriptor) pointer, distinguished by a tag?
tpoacher
What's a "trampoline"?
mbeavitt
Why would someone want to use a nested function, practically speaking?