From 89fee74a0f066dfd73830a7b5fa137e87888c870 Mon Sep 17 00:00:00 2001 From: Emilio G. Cota Date: Thu, 7 Apr 2016 13:19:22 -0400 Subject: tb: consistently use uint32_t for tb->flags We are inconsistent with the type of tb->flags: usage varies loosely between int and uint64_t. Settle to uint32_t everywhere, which is superior to both: at least one target (aarch64) uses the most significant bit in the u32, and uint64_t is wasteful. Compile-tested for all targets. Suggested-by: Laurent Desnogues Suggested-by: Richard Henderson Tested-by: Edgar E. Iglesias Reviewed-by: Edgar E. Iglesias Reviewed-by: Laurent Desnogues Signed-off-by: Emilio G. Cota Signed-off-by: Richard Henderson Message-Id: <1460049562-23517-1-git-send-email-cota@braap.org> --- exec.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'exec.c') diff --git a/exec.c b/exec.c index c4f9036184..ee45472cab 100644 --- a/exec.c +++ b/exec.c @@ -2087,7 +2087,7 @@ static void check_watchpoint(int offset, int len, MemTxAttrs attrs, int flags) target_ulong pc, cs_base; target_ulong vaddr; CPUWatchpoint *wp; - int cpu_flags; + uint32_t cpu_flags; if (cpu->watchpoint_hit) { /* We re-entered the check after replacing the TB. Now raise -- cgit v1.2.3-55-g7522