We'd like to add arguments to the backtrace in Oops messages to make debugging
from these reports more efficient. It is particularly useful for determining
where the problem was generated, particularly when bad pointers are passed in.
This is for production embedded devices with optimized code and which reboot
immediately after storing or sending the Oops message. Performance is an issue,
but the overhead of storing the arguments on the stack is likely worth the
added debug info.
From: Dominic Sweetman [mailto:firstname.lastname@example.org]
Sent: Tue 11/22/2005 4:41 AM
To: Ralf Baechle
Cc: Knittel, Brian; email@example.com
Subject: Re: Saving arguments on the stack
> > I'd like to force the compiler to store arguments on the stack
> > with otherwise optimized code.
Sounds like you're out of luck. Perhaps you'd do better to go one
step back and explain what you're trying to do?