+Thomas
On 11/2/22 00:19, Richard Henderson wrote:
On 2/10/22 10:00, Philippe Mathieu-Daudé wrote:
Move user-mode specific prototypes from "exec/exec-all.h"
to "user/cpu-target.h".
Signed-off-by: Philippe Mathieu-Daudé<f4...@amsat.org>
---
Why a new cpu-target.h, and what is it supposed to mean? What else is
going in there? It all looks cpu_loop related so far.
I'd like to put all declarations using target_ulong in foo-target.h and
the ones which don't in foo-common.h (cpu, user, exec).
That way I can move implementations from target-specific to target
agnostic meson source set, and better isolate the target-specific APIs.
Why is this separate from the next patch, with "cpu-common.h", which
also appears to be basically cpu_loop related?
I can squash both. The commit description could be "Move APIs using
target_ulong to cpu-target.h, keep the rest in cpu-common.h".
