This is a left over erroneous check from the days front-ends handled
io start/end themselves. Regardless just because IO could be performed
on the last instruction doesn't obligate the front end to do so.
This fixes an abort faced by the aspeed execute-in-place support which
will necessarily trigger this state (even before the one-shot
CF_LAST_IO fix). The test still seems to hang once it attempts to boot
the Linux kernel but I suspect this is an unrelated issue with icount
and the timer handling code.
Signed-off-by: Alex Bennée<alex.bennee@linaro.org>
Cc: Cédric Le Goater<clg@kaod.org>
---
target/arm/translate.c | 5 -----
1 file changed, 5 deletions(-)