From: Matheus Ferst <matheus.ferst@eldorado.org.br>

This patch series fixes some uses of env->xer that were left behind when
SO, OV, and CA bits were separated into other fields of CPUPPCState. At
the time, all of them weren't in target-specific files/directories,
which probably made it harder to track what needed to be changed.
Currently, this still is the case for linux-user/elfload.c. Is there
any particular reason for that? I can try to provide a patch to split
it.

Matheus Ferst (4):
  linux-user/ppc: Fix XER access in save/restore_user_regs
  target/ppc: Fix XER access in gdbstub
  linux-user: Fix XER access in ppc version of elf_core_copy_regs
  target/ppc: Fix XER access in monitor

 linux-user/elfload.c                        |  2 +-
 linux-user/ppc/signal.c                     |  9 +++--
 target/ppc/cpu.c                            |  2 +-
 target/ppc/cpu.h                            |  2 +-
 target/ppc/gdbstub.c                        |  8 ++--
 target/ppc/monitor.c                        |  9 ++++-
 tests/tcg/ppc64/Makefile.target             |  2 +
 tests/tcg/ppc64le/Makefile.target           |  2 +
 tests/tcg/ppc64le/signal_save_restore_xer.c | 42 +++++++++++++++++++++
 9 files changed, 67 insertions(+), 11 deletions(-)
 create mode 100644 tests/tcg/ppc64le/signal_save_restore_xer.c

-- 
2.25.1