From: Michael Tokarev <mjt@tls.msk.ru>
To: Peter Maydell <peter.maydell@linaro.org>,
Chen Gang <gang.chen.5i5j@gmail.com>
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
qemu-devel <qemu-devel@nongnu.org>,
"rth@twiddle.net" <rth@twiddle.net>
Subject: Re: [Qemu-trivial] [PATCH] disas/libvixl/a64/instructions-a64.h: Remove useless varialbe to avoid building break with '-Werror'
Date: Thu, 23 Oct 2014 10:49:09 +0400 [thread overview]
Message-ID: <5448A4E5.1020605@msgid.tls.msk.ru> (raw)
In-Reply-To: <CAFEAcA9KgX1gOtXPqTC2gX1HD69aPF9fbKkk1i5zbN2+tLW_og@mail.gmail.com>
On 10/21/2014 07:50 PM, Peter Maydell wrote:
> On 9 October 2014 15:00, Chen Gang <gang.chen.5i5j@gmail.com> wrote:
[]
>> --- a/disas/libvixl/a64/instructions-a64.h
>> +++ b/disas/libvixl/a64/instructions-a64.h
>> @@ -95,30 +95,6 @@ const unsigned kDoubleExponentBits = 11;
>> const unsigned kFloatMantissaBits = 23;
>> const unsigned kFloatExponentBits = 8;
>>
>> -const float kFP32PositiveInfinity = rawbits_to_float(0x7f800000);
>> -const float kFP32NegativeInfinity = rawbits_to_float(0xff800000);
...
> Upstream's plan for fixing this is to turn these into
> 'extern const double foo' in the header with the definition
> in an appropriate .cc file. Given that, I think I'm happy for
> us to take this patch in QEMU for the moment, with the expectation
> that the next libvixl drop will just obsolete it.
If upstream already have a patch for this, why not take the
upstream's solution now, so we wont need to revert our solution
before applying next drop from upstream?
BTW, how the "upstream drop" is done, anyway? If it is something
like git merge, we may need to care, but if it is just cp -a upstream/* .
when there's no reason to... ;)
Thanks,
/mjt
WARNING: multiple messages have this Message-ID (diff)
From: Michael Tokarev <mjt@tls.msk.ru>
To: Peter Maydell <peter.maydell@linaro.org>,
Chen Gang <gang.chen.5i5j@gmail.com>
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
qemu-devel <qemu-devel@nongnu.org>,
"rth@twiddle.net" <rth@twiddle.net>
Subject: Re: [Qemu-devel] [Qemu-trivial] [PATCH] disas/libvixl/a64/instructions-a64.h: Remove useless varialbe to avoid building break with '-Werror'
Date: Thu, 23 Oct 2014 10:49:09 +0400 [thread overview]
Message-ID: <5448A4E5.1020605@msgid.tls.msk.ru> (raw)
In-Reply-To: <CAFEAcA9KgX1gOtXPqTC2gX1HD69aPF9fbKkk1i5zbN2+tLW_og@mail.gmail.com>
On 10/21/2014 07:50 PM, Peter Maydell wrote:
> On 9 October 2014 15:00, Chen Gang <gang.chen.5i5j@gmail.com> wrote:
[]
>> --- a/disas/libvixl/a64/instructions-a64.h
>> +++ b/disas/libvixl/a64/instructions-a64.h
>> @@ -95,30 +95,6 @@ const unsigned kDoubleExponentBits = 11;
>> const unsigned kFloatMantissaBits = 23;
>> const unsigned kFloatExponentBits = 8;
>>
>> -const float kFP32PositiveInfinity = rawbits_to_float(0x7f800000);
>> -const float kFP32NegativeInfinity = rawbits_to_float(0xff800000);
...
> Upstream's plan for fixing this is to turn these into
> 'extern const double foo' in the header with the definition
> in an appropriate .cc file. Given that, I think I'm happy for
> us to take this patch in QEMU for the moment, with the expectation
> that the next libvixl drop will just obsolete it.
If upstream already have a patch for this, why not take the
upstream's solution now, so we wont need to revert our solution
before applying next drop from upstream?
BTW, how the "upstream drop" is done, anyway? If it is something
like git merge, we may need to care, but if it is just cp -a upstream/* .
when there's no reason to... ;)
Thanks,
/mjt
next prev parent reply other threads:[~2014-10-23 6:49 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-09 14:00 [Qemu-trivial] [PATCH] disas/libvixl/a64/instructions-a64.h: Remove useless varialbe to avoid building break with '-Werror' Chen Gang
2014-10-09 14:00 ` [Qemu-devel] " Chen Gang
2014-10-09 14:34 ` [Qemu-trivial] " Peter Maydell
2014-10-09 14:34 ` [Qemu-devel] " Peter Maydell
2014-10-10 1:54 ` [Qemu-trivial] " Chen Gang
2014-10-10 1:54 ` [Qemu-devel] " Chen Gang
2014-10-10 7:37 ` [Qemu-trivial] " Peter Maydell
2014-10-10 7:37 ` [Qemu-devel] " Peter Maydell
2014-10-10 8:53 ` [Qemu-trivial] " Chen Gang
2014-10-10 8:53 ` [Qemu-devel] " Chen Gang
2014-10-10 9:03 ` [Qemu-trivial] " Chen Gang
2014-10-10 9:03 ` [Qemu-devel] " Chen Gang
2014-10-09 14:54 ` [Qemu-trivial] " Eric Blake
2014-10-09 14:54 ` Eric Blake
2014-10-10 1:28 ` [Qemu-trivial] " Chen Gang
2014-10-10 1:28 ` Chen Gang
2014-10-21 15:50 ` [Qemu-trivial] " Peter Maydell
2014-10-21 15:50 ` [Qemu-devel] " Peter Maydell
2014-10-23 6:49 ` Michael Tokarev [this message]
2014-10-23 6:49 ` [Qemu-devel] [Qemu-trivial] " Michael Tokarev
2014-10-23 7:14 ` Peter Maydell
2014-10-23 7:14 ` [Qemu-devel] " Peter Maydell
2014-10-23 8:09 ` Michael Tokarev
2014-10-23 8:09 ` [Qemu-devel] " Michael Tokarev
2014-10-23 9:02 ` Peter Maydell
2014-10-23 9:02 ` [Qemu-devel] " Peter Maydell
2014-10-23 10:09 ` Peter Maydell
2014-10-23 10:09 ` [Qemu-devel] " Peter Maydell
2014-10-23 10:27 ` Michael Tokarev
2014-10-23 10:27 ` [Qemu-devel] " Michael Tokarev
2014-10-23 11:05 ` Peter Maydell
2014-10-23 11:05 ` [Qemu-devel] " Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2014-10-21 23:27 Chen Gang
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=5448A4E5.1020605@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=gang.chen.5i5j@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=rth@twiddle.net \
/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.