qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: Michael Mueller <mimu@linux.vnet.ibm.com>, qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] virtio-input: const_le16 and const_le32 not build time constant
Date: Mon, 01 Jun 2015 22:22:49 +0200	[thread overview]
Message-ID: <556CBF19.2050302@suse.de> (raw)
In-Reply-To: <1433166716-36861-1-git-send-email-mimu@linux.vnet.ibm.com>



On 01.06.15 15:51, Michael Mueller wrote:
> As the implementation of const_le16 and const_le32 is not build time constant
> on big endian systems this need to be fixed.
> 
>   CC    hw/input/virtio-input-hid.o
> hw/input/virtio-input-hid.c:340:13: error: initializer element is not constant
> hw/input/virtio-input-hid.c:340:13: error: (near initialization for ‘virtio_keyboard_config[1].u.ids.bustype’)
> ...
> 
> Signed-off-by: Michael Mueller <mimu@linux.vnet.ibm.com>

Thanks a lot for this patch. It fixes current compile breakage on
upstream QEMU for me - or on any big endian system for that matter.

For the time being I've included it into my ppc-next tree, but I'd
prefer if this gets merged directly before I flush it (for
bisectability's sake).


Alex

> ---
>  include/hw/virtio/virtio-input.h | 10 ++++++++--
>  1 file changed, 8 insertions(+), 2 deletions(-)
> 
> diff --git a/include/hw/virtio/virtio-input.h b/include/hw/virtio/virtio-input.h
> index a265519..bcee355 100644
> --- a/include/hw/virtio/virtio-input.h
> +++ b/include/hw/virtio/virtio-input.h
> @@ -14,8 +14,14 @@ typedef struct virtio_input_config virtio_input_config;
>  typedef struct virtio_input_event virtio_input_event;
>  
>  #if defined(HOST_WORDS_BIGENDIAN)
> -# define const_le32(_x) bswap32(_x)
> -# define const_le16(_x) bswap32(_x)
> +# define const_le32(_x)                          \
> +    (((_x & 0x000000ffU) << 24) |                \
> +     ((_x & 0x0000ff00U) <<  8) |                \
> +     ((_x & 0x00ff0000U) >>  8) |                \
> +     ((_x & 0xff000000U) >> 24))
> +# define const_le16(_x)                          \
> +    (((_x & 0x00ff) << 8) |                      \
> +     ((_x & 0xff00) >> 8))
>  #else
>  # define const_le32(_x) (_x)
>  # define const_le16(_x) (_x)
> 

  reply	other threads:[~2015-06-01 20:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-01 13:51 [Qemu-devel] [PATCH] virtio-input: const_le16 and const_le32 not build time constant Michael Mueller
2015-06-01 20:22 ` Alexander Graf [this message]
2015-06-02  7:31 ` Christian Borntraeger
2015-06-02 12:20   ` Peter Maydell

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=556CBF19.2050302@suse.de \
    --to=agraf@suse.de \
    --cc=kraxel@redhat.com \
    --cc=mimu@linux.vnet.ibm.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /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).