On Sun, 1 May 2022 at 07:17, Richard Henderson <richard.hender...@linaro.org> wrote: > > Perform the override check early, so that it is still done > even when we decide to discard an unreachable cpreg. > > Use assert not printf+abort. > > Signed-off-by: Richard Henderson <richard.hender...@linaro.org> > --- > target/arm/helper.c | 22 ++++++++-------------- > 1 file changed, 8 insertions(+), 14 deletions(-)
The reason I put the printf in here originally was that I felt the conditionality with which we define cpregs was complicated enough that conflicting cpreg definitions might be found not by the developer writing new code but perhaps by users in the field who used rarer CPU types or oddball feature enable combinations, and I wanted the reports to provide enough detail to identify the conflicting registers without having to repro running under a debugger to print out the values of oldreg and r2. Still, I suppose it's N years later and we haven't in fact particularly had that kind of bug report, so it's not strictly necessary. Reviewed-by: Peter Maydell <peter.mayd...@linaro.org> thanks -- PMM
