From: "Andreas Färber" <afaerber@suse.de>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] softfloat: fix for C99
Date: Tue, 27 Dec 2011 17:15:19 +0100 [thread overview]
Message-ID: <4EF9EF17.4050703@suse.de> (raw)
In-Reply-To: <1324998680-16003-1-git-send-email-avi@redhat.com>
Am 27.12.2011 16:11, schrieb Avi Kivity:
> C99 appears to consider compound literals as non-constants, and complains
> when they are used in static initializers. Switch to ordinary initializer
> syntax.
>
> Signed-off-by: Avi Kivity <avi@redhat.com>
Acked-by: Andreas Färber <afaerber@suse.de>
For the record, tested with --extra-cflags=-std=gnu99.
> diff --git a/fpu/softfloat-specialize.h b/fpu/softfloat-specialize.h
> index c5e2dab..4902450 100644
> --- a/fpu/softfloat-specialize.h
> +++ b/fpu/softfloat-specialize.h
> @@ -89,8 +89,8 @@ const float64 float64_default_nan = const_float64(LIT64( 0xFFF8000000000000 ));
> #define floatx80_default_nan_low LIT64( 0xC000000000000000 )
> #endif
>
> -const floatx80 floatx80_default_nan = make_floatx80(floatx80_default_nan_high,
> - floatx80_default_nan_low);
> +const floatx80 floatx80_default_nan
> + = make_floatx80_init(floatx80_default_nan_high, floatx80_default_nan_low);
Calling it init_floatx80 would avoid the line break, but I'm okay with
it either way.
Thanks,
Andreas
$ gcc --version
gcc (SUSE Linux) 4.6.2
Copyright (C) 2011 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2011-12-27 16:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-27 15:11 [Qemu-devel] [PATCH] softfloat: fix for C99 Avi Kivity
2011-12-27 16:15 ` Andreas Färber [this message]
2012-02-09 16:20 ` Andreas Färber
2012-02-09 16:38 ` Avi Kivity
2012-03-16 10:01 ` Andreas Färber
2012-03-17 16:24 ` Blue Swirl
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=4EF9EF17.4050703@suse.de \
--to=afaerber@suse.de \
--cc=avi@redhat.com \
--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).