From: Jan Kiszka <jan.kiszka@web.de>
To: Stefan Weil <sw@weilnetz.de>, qemu-devel <qemu-devel@nongnu.org>
Cc: peter.maydell@linaro.org
Subject: Re: [Qemu-devel] [PATCH v2] cpu-exec: Fix compiler warning (-Werror=clobbered)
Date: Thu, 31 Oct 2013 20:41:40 +0100 [thread overview]
Message-ID: <5272B274.8040001@web.de> (raw)
In-Reply-To: <1383247916-2660-1-git-send-email-sw@weilnetz.de>
[-- Attachment #1: Type: text/plain, Size: 2353 bytes --]
On 2013-10-31 20:31, Stefan Weil wrote:
> 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 ‘cpu’ might be clobbered by ‘longjmp’ or ‘vfork’ [-Werror=clobbered]
> cpu-exec.c:207:15: error:
> variable ‘cc’ might be clobbered by ‘longjmp’ or ‘vfork’ [-Werror=clobbered]
> cpu-exec.c:202:28: error:
> argument ‘env’ might be clobbered by ‘longjmp’ or ‘vfork’ [-Werror=clobbered]
>
> 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 <sw@weilnetz.de>
> ---
>
> 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 clang.
> + * Reload essential local variables here for those compilers.
> + * gcc 4.7 would complain about this code (-Wclobbered). */
> cpu = current_cpu;
> env = cpu->env_ptr;
> #if !(defined(CONFIG_USER_ONLY) && \
> (defined(TARGET_M68K) || defined(TARGET_PPC) || defined(TARGET_S390X)))
> cc = CPU_GET_CLASS(cpu);
> #endif
> +#endif /* __clang__ or old gcc */
> }
> } /* for(;;) */
>
>
Are all clang versions affected? Then this looks reasonable.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2013-10-31 19:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 19:31 [Qemu-devel] [PATCH v2] cpu-exec: Fix compiler warning (-Werror=clobbered) Stefan Weil
2013-10-31 19:41 ` Jan Kiszka [this message]
2013-10-31 20:03 ` Stefan Weil
2013-11-05 17:52 ` Stefan Weil
2013-11-05 18:00 ` Peter Maydell
2013-11-05 18:03 ` Andreas Färber
2013-11-06 5:40 ` Stefan Weil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5272B274.8040001@web.de \
--to=jan.kiszka@web.de \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.