target/microblaze: Add gdbstub xml
Mirroring the upstream gdb xml files, the two stack boundary registers are separated out. Reviewed-by:Edgar E. Iglesias <edgar@zeroasic.com> Signed-off-by:
Richard Henderson <richard.henderson@linaro.org>
Showing
- configs/targets/microblaze-linux-user.mak 1 addition, 0 deletionsconfigs/targets/microblaze-linux-user.mak
- configs/targets/microblaze-softmmu.mak 1 addition, 0 deletionsconfigs/targets/microblaze-softmmu.mak
- configs/targets/microblazeel-linux-user.mak 1 addition, 0 deletionsconfigs/targets/microblazeel-linux-user.mak
- configs/targets/microblazeel-softmmu.mak 1 addition, 0 deletionsconfigs/targets/microblazeel-softmmu.mak
- gdb-xml/microblaze-core.xml 67 additions, 0 deletionsgdb-xml/microblaze-core.xml
- gdb-xml/microblaze-stack-protect.xml 12 additions, 0 deletionsgdb-xml/microblaze-stack-protect.xml
- target/microblaze/cpu.c 6 additions, 1 deletiontarget/microblaze/cpu.c
- target/microblaze/cpu.h 2 additions, 0 deletionstarget/microblaze/cpu.h
- target/microblaze/gdbstub.c 34 additions, 11 deletionstarget/microblaze/gdbstub.c
gdb-xml/microblaze-core.xml
0 → 100644
gdb-xml/microblaze-stack-protect.xml
0 → 100644
Please register or sign in to comment