Re: [RFC PATCH 1/5] Rename the singlestep global variable to one_insn_per_tb

2023-02-10 Thread Peter Maydell
On Mon, 6 Feb 2023 at 20:20, Thomas Huth wrote: > > On 06/02/2023 18.13, Peter Maydell wrote: > > The 'singlestep' global variable is badly misnamed, because it has > > nothing to do with single-stepping the emulation either via the gdb > > stub or by emulation of architectural debug facilities.

Re: [RFC PATCH 1/5] Rename the singlestep global variable to one_insn_per_tb

2023-02-06 Thread Thomas Huth
On 06/02/2023 18.13, Peter Maydell wrote: The 'singlestep' global variable is badly misnamed, because it has nothing to do with single-stepping the emulation either via the gdb stub or by emulation of architectural debug facilities. Instead what it does is force TCG to put only one instruction i

[RFC PATCH 1/5] Rename the singlestep global variable to one_insn_per_tb

2023-02-06 Thread Peter Maydell
The 'singlestep' global variable is badly misnamed, because it has nothing to do with single-stepping the emulation either via the gdb stub or by emulation of architectural debug facilities. Instead what it does is force TCG to put only one instruction into each TB. Rename it to one_insn_per_tb, s