From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43302) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VbxyR-0007N4-4N for qemu-devel@nongnu.org; Thu, 31 Oct 2013 15:32:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VbxyM-0001yV-82 for qemu-devel@nongnu.org; Thu, 31 Oct 2013 15:32:07 -0400 Received: from qemu.weilnetz.de ([37.221.198.45]:42110 helo=v2201305906712890.yourvserver.net) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VbxyM-0001yQ-1b for qemu-devel@nongnu.org; Thu, 31 Oct 2013 15:32:02 -0400 From: Stefan Weil Date: Thu, 31 Oct 2013 20:31:56 +0100 Message-Id: <1383247916-2660-1-git-send-email-sw@weilnetz.de> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: [Qemu-devel] [PATCH v2] cpu-exec: Fix compiler warning (-Werror=clobbered) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel Cc: peter.maydell@linaro.org, jan.kiszka@web.de, Stefan Weil Reloading of local variables after sigsetjmp is only needed for some buggy compilers. The code which should reload these variables causes compiler warnings with gcc 4.7 when compiler optimizations are enabled: cpu-exec.c:204:15: error: variable =E2=80=98cpu=E2=80=99 might be clobbered by =E2=80=98longjmp=E2= =80=99 or =E2=80=98vfork=E2=80=99 [-Werror=3Dclobbered] cpu-exec.c:207:15: error: variable =E2=80=98cc=E2=80=99 might be clobbered by =E2=80=98longjmp=E2=80= =99 or =E2=80=98vfork=E2=80=99 [-Werror=3Dclobbered] cpu-exec.c:202:28: error: argument =E2=80=98env=E2=80=99 might be clobbered by =E2=80=98longjmp=E2= =80=99 or =E2=80=98vfork=E2=80=99 [-Werror=3Dclobbered] Now this code is only used for compilers which need it (and gcc 4.5.x, x > 0 which does not need it but won't give warnings). There were bug reports for clang and gcc 4.5.0, while gcc 4.5.1 was reported to work fine without the reload code. Signed-off-by: Stefan Weil --- v2: Don't remove the code which causes the warnings, but use it only with clang or gcc < 4.6. cpu-exec.c | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/cpu-exec.c b/cpu-exec.c index 30cfa2a..fec20c3 100644 --- a/cpu-exec.c +++ b/cpu-exec.c @@ -677,14 +677,18 @@ int cpu_exec(CPUArchState *env) only be set by a memory fault) */ } /* for(;;) */ } else { - /* Reload env after longjmp - the compiler may have smashed = all - * local variables as longjmp is marked 'noreturn'. */ +#if defined(__clang__) || !QEMU_GNUC_PREREQ(4, 6) + /* Some compilers wrongly smash all local variables after + * siglongjmp. There were bug reports for gcc 4.5.0 and clan= g. + * Reload essential local variables here for those compilers= . + * gcc 4.7 would complain about this code (-Wclobbered). */ cpu =3D current_cpu; env =3D cpu->env_ptr; #if !(defined(CONFIG_USER_ONLY) && \ (defined(TARGET_M68K) || defined(TARGET_PPC) || defined(TARGET_S39= 0X))) cc =3D CPU_GET_CLASS(cpu); #endif +#endif /* __clang__ or old gcc */ } } /* for(;;) */ =20 --=20 1.7.10.4