glibc 3.0

by · Sep 9, 2017 · 1,011 views ·

This session intends to provide a forum for glibc developers to discuss current pain points and past mistakes leading to them. We want to see if we can correct at least some of them with a slight risk to full backwards compatibility. Some examples of what we might want to remove: - libio vtables for an old C++ ABI (predating most current targets) - malloc hooks - flushing stdio streams on abort/assert/corruption of stack/heap