> Is there any to leave _G_IO_NO_BACKWARD_COMPAT undefined in a new > glibc port? I believe defining this macro will make libio somewhat > faster. I can't see any reason not to define it, as you say. That has not been tested so there is likely to be some bit-rot, but that is easily fixed.