From: "Andreas Färber" <andreas.faerber@web.de>
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org, Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] Build breakage on OpenSolaris - softfloat
Date: Sun, 01 May 2011 20:26:50 +0200 [thread overview]
Message-ID: <4DBDA5EA.7070708@web.de> (raw)
In-Reply-To: <4DBD7D0C.4050106@web.de>
Andreas Färber schrieb:
> CC i386-softmmu/op_helper.o
> /export/home/andreas/QEMU/qemu/target-i386/op_helper.c:110: error:
> initializer element is not constant
> /export/home/andreas/QEMU/qemu/target-i386/op_helper.c:110: error:
> (near initialization for `f15rk[0]')
> /export/home/andreas/QEMU/qemu/target-i386/op_helper.c:111: error:
> initializer element is not constant
> /export/home/andreas/QEMU/qemu/target-i386/op_helper.c:111: error:
> (near initialization for `f15rk[1]')
> /export/home/andreas/QEMU/qemu/target-i386/op_helper.c:112: error:
> initializer element is not constant
> /export/home/andreas/QEMU/qemu/target-i386/op_helper.c:112: error:
> (near initialization for `f15rk[2]')
> /export/home/andreas/QEMU/qemu/target-i386/op_helper.c:113: error:
> initializer element is not constant
> /export/home/andreas/QEMU/qemu/target-i386/op_helper.c:113: error:
> (near initialization for `f15rk[3]')
> /export/home/andreas/QEMU/qemu/target-i386/op_helper.c:114: error:
> initializer element is not constant
> /export/home/andreas/QEMU/qemu/target-i386/op_helper.c:114: error:
> (near initialization for `f15rk[4]')
> /export/home/andreas/QEMU/qemu/target-i386/op_helper.c:115: error:
> initializer element is not constant
> /export/home/andreas/QEMU/qemu/target-i386/op_helper.c:115: error:
> (near initialization for `f15rk[5]')
> /export/home/andreas/QEMU/qemu/target-i386/op_helper.c:116: error:
> initializer element is not constant
> /export/home/andreas/QEMU/qemu/target-i386/op_helper.c:116: error:
> (near initialization for `f15rk[6]')
> gmake[1]: *** [op_helper.o] Error 1
> make: *** [subdir-i386-softmmu] Error 2
>
> Looks like an issue with make_floatx80().
As suggested by Peter, I inspected the op_helper.c preprocessor output:
# 108 "/export/home/andreas/QEMU/qemu/target-i386/op_helper.c"
static const CPU86_LDouble f15rk[7] =
{
((floatx80) { 0x0000000000000000LL, 0x0000 }),
((floatx80) { 0x8000000000000000LL, 0x3fff }),
((floatx80) { 0xc90fdaa22168c235LL, 0x4000 }),
((floatx80) { 0x9a209a84fbcff799LL, 0x3ffd }),
((floatx80) { 0xb17217f7d1cf79acLL, 0x3ffe }),
((floatx80) { 0xb8aa3b295c17f0bcLL, 0x3fff }),
((floatx80) { 0xd49a784bcd1b8afeLL, 0x4000 }),
};
Doesn't look unexpected.
typedef floatx80 CPU86_LDouble;
and
# 153 "/export/home/andreas/QEMU/qemu/fpu/softfloat.h"
typedef struct {
uint64_t low;
uint16_t high;
} floatx80;
look okay, too.
Andreas
next prev parent reply other threads:[~2011-05-01 18:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-01 15:32 [Qemu-devel] Build breakage on OpenSolaris - softfloat Andreas Färber
2011-05-01 18:26 ` Andreas Färber [this message]
2011-05-04 19:45 ` Andreas Färber
2011-05-15 11:55 ` Aurelien Jarno
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=4DBDA5EA.7070708@web.de \
--to=andreas.faerber@web.de \
--cc=aurelien@aurel32.net \
--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).