[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1258661836.22249.995.camel@gandalf.stny.rr.com>
Date: Thu, 19 Nov 2009 15:17:16 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Frederic Weisbecker <fweisbec@...il.com>
Cc: David Daney <ddaney@...iumnetworks.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Haley <aph@...hat.com>,
Richard Guenther <richard.guenther@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
LKML <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Heiko Carstens <heiko.carstens@...ibm.com>,
feng.tang@...el.com, Peter Zijlstra <peterz@...radead.org>,
jakub@...hat.com, gcc@....gnu.org
Subject: Re: BUG: GCC-4.4.x changes the function frame on some functions
On Thu, 2009-11-19 at 15:05 -0500, Steven Rostedt wrote:
> Well, other archs use a register to store the return address. But it
> would also be easy to do (pseudo arch assembly):
>
> <function>:
> mov lr, (%sp)
> add 8, %sp
> blr __fentry__
Should be bl __fentry__ for "branch and link".
> sub 8, %sp
> mov (%sp), lr
>
>
> That way the lr would have the current function, and the parent would
> still be at 8(%sp)
Actually, if we add a new profiler and can make our own specification, I
would say that the add and sub lines be the responsibility of
__fentry__. Then we would have:
<function>:
mov lr, (%sp)
bl __fentry__
mov (%sp), lr
If sp points to the current content, then replace (%sp) above with
-8(%sp). Then the implementation of a nop __fentry__ would simply be:
__fentry__:
blr
For anything more elaborate, __fentry__ would be responsible for all
adjustments.
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists