Browse Source
a2, a3; zero at v0 v1 a0 a1 a2 a3 00000000 00000000 00000000 00000000 00000004 8afffee0 8affff30 8f121b30 t0 t1 t2 t3 t4 t5 t6 t7 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 s0 s1 s2 s3 s4 s5 s6 s7 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 t8 t9 k0 k1 gp sp s8 ra 00000000 00000000 00000000 00000000 00000000 8afffec0 00000000 8f0aa510 this may cause the param is modified by kernel; change the client stack to reserved pmon area, so the param allocated on stack is safe; zero at v0 v1 a0 a1 a2 a3 00000000 00000000 00000000 00000000 00000004 8f00fee0 8f00ff30 8f121b50 t0 t1 t2 t3 t4 t5 t6 t7 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 s0 s1 s2 s3 s4 s5 s6 s7 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 t8 t9 k0 k1 gp sp s8 ra 00000000 00000000 00000000 00000000 00000000 8f00fec0 00000000 8f0aa510 ps: set boot_param to be static allocated causing other error, so we have to do this way; submitted by 'Qiao Chong' <qiaochong@loongson.cn> Change-Id: I02d9de3ff0e679ca1786cd387532fde0344249f2master
Huang Pei
10 years ago
1 changed files with 2 additions and 1 deletions
Loading…
Reference in new issue