qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Liviu Ionescu <ilg@livius.net>, Stefan Weil <sw@weilnetz.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU 2.4 for Windows - current status
Date: Wed, 5 Aug 2015 18:56:59 +0200	[thread overview]
Message-ID: <55C2405B.4050008@redhat.com> (raw)
In-Reply-To: <E0CEE935-6984-4758-9DBE-BB1737CAD6D6@livius.net>



On 05/08/2015 18:51, Liviu Ionescu wrote:
> 
>> On 05 Aug 2015, at 14:03, Stefan Weil <sw@weilnetz.de> wrote:
>>
>> Fix sigsetjmp for w64
>> http://repo.or.cz/w/qemu/ar7.git/commit/8fa9c07c9a33174905e67589bea6be3e278712cb
> 
> 
> I tried to apply your patch to my branch and I got:
> 
> Running QEMU make install...
>   CC    gnuarmeclipse-softmmu/cpu-exec.o
> /Host/Work/qemu/gnuarmeclipse-qemu.git/cpu-exec.c:37:0: warning: "sigsetjmp" redefined
>  #define sigsetjmp(env, savesigs) _setjmp(env, NULL)
>  ^
> In file included from /Host/Work/qemu/gnuarmeclipse-qemu.git/include/qemu-common.h:47:0,
>                  from /Host/Work/qemu/gnuarmeclipse-qemu.git/target-arm/cpu.h:39,
>                  from /Host/Work/qemu/gnuarmeclipse-qemu.git/cpu-exec.c:20:
> /Host/Work/qemu/gnuarmeclipse-qemu.git/include/sysemu/os-win32.h:72:0: note: this is the location of the previous definition
>  #define sigsetjmp(env, savemask) setjmp(env)
>  ^
> 
> 
> I did not check the latest version in the repository (waiting for
> 2.4), but could you verify, maybe a better location for your patch
> would be in os-win32.h?

os-win32.h has the following already:

#if defined(_WIN64)
# undef setjmp
# define setjmp(env) _setjmp(env, NULL)
#endif
#define sigjmp_buf jmp_buf
#define sigsetjmp(env, savemask) setjmp(env)


And Stefan's patch has this in cpu-exec.c:

#if defined(_WIN64)
#define sigsetjmp(env, savesigs) _setjmp(env, NULL)
#endif

The above should not be necessary if the definition of sigsetjmp is
already picked up from os-win32.h.

Since os-win32.h is usually included through qemu-common.h, my guess was
that cpu-exec.c was missing an inclusion of qemu-common.h.  However, all
target-*/cpu.h files include qemu-common.h, so I am not sure why things
break for Stefan...

Paolo

  reply	other threads:[~2015-08-05 16:57 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-31 10:17 [Qemu-devel] [PATCH for-2.4] oslib-win32: only provide localtime_r/gmtime_r if missing Daniel P. Berrange
2015-07-31 12:49 ` Paolo Bonzini
2015-07-31 13:33   ` Daniel P. Berrange
2015-07-31 17:58   ` Stefan Weil
2015-08-05  9:52     ` Daniel P. Berrange
2015-08-05 11:03       ` [Qemu-devel] QEMU 2.4 for Windows - current status Stefan Weil
2015-08-05 12:49         ` Paolo Bonzini
2015-08-05 15:38           ` Stefan Weil
2015-09-10 20:38           ` Stefan Weil
2015-08-05 16:51         ` Liviu Ionescu
2015-08-05 16:56           ` Paolo Bonzini [this message]
2015-08-05 18:39             ` Liviu Ionescu
2015-08-05 20:30               ` Stefan Weil
2015-08-05 21:42                 ` Liviu Ionescu
2015-08-06  8:44                 ` Kevin Wolf
2015-08-06 10:12                   ` Stefan Weil
2015-08-06 17:12                     ` Richard Henderson
2015-08-10 10:25         ` Peter Maydell
2015-08-10 11:39           ` Stefan Weil
2015-08-10 14:00             ` Paolo Bonzini
2015-08-10 20:22               ` 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=55C2405B.4050008@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=ilg@livius.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).