what is the purpose of replacing the magic numbers with code analysis?
And what will happen when you run userland with MIPS16 or MIPS16e code?
We have it on our work-list to eventually clean up all the places in the
kernel that inspect code to allow MIPS16(e) code as well, so adding more
code inspection points is a bad idea unless it really is necessary.
Atsushi Nemoto writes:
> Content-Type: Text/Plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
> There are some magic constant numbers about stack layout in
> thread_saved_pc() and get_wchan() function.
> I made a patch to eliminate these magic numbers. This patch analyzes
> some functions prologue codes in heuristic way at run-time. "ps -l"
> (and "MAGIC SYSRQ" feature) works fine with this patch.
> Atsushi Nemoto