This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: BUG: GCC-4.4.x changes the function frame on some functions
- From: "H. Peter Anvin" <hpa at zytor dot com>
- To: Jeff Law <law at redhat dot com>
- Cc: rostedt at goodmis dot org, David Daney <ddaney at caviumnetworks dot com>, Linus Torvalds <torvalds at linux-foundation dot org>, Andrew Haley <aph at redhat dot com>, Richard Guenther <richard dot guenther at gmail dot com>, Thomas Gleixner <tglx at linutronix dot de>, Ingo Molnar <mingo at elte dot hu>, LKML <linux-kernel at vger dot kernel dot org>, Andrew Morton <akpm at linux-foundation dot org>, Heiko Carstens <heiko dot carstens at de dot ibm dot com>, feng dot tang at intel dot com, Fr??d??ric Weisbecker <fweisbec at gmail dot com>, Peter Zijlstra <peterz at infradead dot org>, jakub at redhat dot com, gcc at gcc dot gnu dot org
- Date: Thu, 19 Nov 2009 13:14:18 -0800
- Subject: Re: BUG: GCC-4.4.x changes the function frame on some functions
Hence a new unconstrained option...
"Jeff Law" <law@redhat.com> wrote:
>On 11/19/09 12:50, H. Peter Anvin wrote:
>>
>> Calling the profiler immediately at the entry point is clearly the more
>> sane option. It means the ABI is well-defined, stable, and independent
>> of what the actual function contents are. It means that ABI isn't the
>> normal C ABI (the __fentry__ function would have to preserve all
>> registers), but that's fine...
>>
>Note there are targets (even some old x86 variants) that required the
>profiling calls to occur after the prologue. Unfortunately, nobody
>documented *why* that was the case. Sigh.
>
>Jeff
--
Sent from my mobile phone. Please excuse any lack of formatting.