https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71496
Tobias Netzel <tobias.netzel at googlemail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tobias.netzel at googlemail dot co | |m --- Comment #6 from Tobias Netzel <tobias.netzel at googlemail dot com> --- This fix seems to have had an unwanted sideeffect: When not compiling with -fno-PIC or -mdynamic-no-pic the compiler for any compiled function unconditionally saves and restores R31 from/to the stack even when it's not touched at all. I've verified that gcc 4.2 (Apple's version), gcc 4.9 and 5.4 don't do that. But while gcc 4.9 and 5.4 do unconditionally save and restore R31 when -pg is passed, Apple's gcc 4.2 doesn't even do it then. Appearantly the interpretation of what Apple meant with the sentence "This cannot happen with -fPIC because the PIC register (R31) is always "used" in the sense checked by the consistency check." might need to be revised.