qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Bastian Koppelmann <kbastian@mail.uni-paderborn.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 00/10] tricore-patches
Date: Wed, 23 Mar 2016 09:17:59 +0100	[thread overview]
Message-ID: <56F25137.5020807@mail.uni-paderborn.de> (raw)
In-Reply-To: <CAFEAcA91Z6yGpLD5wKTQz_id+thhj8D=KzN5H8kHXwbigS-38Q@mail.gmail.com>

On 03/22/2016 09:15 PM, Peter Maydell wrote:
> On 22 March 2016 at 13:46, Bastian Koppelmann
> <kbastian@mail.uni-paderborn.de> wrote:
>> The following changes since commit 4829e0378dfb91d55af9dfd741bd09e8f2c4f91a:
>>
>>   Merge remote-tracking branch 'remotes/armbru/tags/pull-qapi-2016-03-18' into staging (2016-03-18 17:18:41 +0000)
>>
>> are available in the git repository at:
>>
>>   https://github.com/bkoppelmann/qemu-tricore-upstream.git tags/pull-tricore-20160322
>>
>> for you to fetch changes up to d66718ccf37b71eff686c3d6116223889736188f:
>>
>>   target-tricore: Add ftoi and itof instructions (2016-03-21 18:04:16 +0100)
> 
> Hi; I'm afraid this doesn't build with clang:
> 
> /home/petmay01/linaro/qemu-for-merges/target-tricore/fpu_helper.c:45:20:
> error: unused function 'f_is_pos_inf' [-Werror,-Wunused-function]
> static inline bool f_is_pos_inf(float32 arg)
>                    ^
> /home/petmay01/linaro/qemu-for-merges/target-tricore/fpu_helper.c:50:20:
> error: unused function 'f_is_neg_inf' [-Werror,-Wunused-function]
> static inline bool f_is_neg_inf(float32 arg)
>    
                ^
Whoops, these functions are not supposed to be there. I'll remove them
and re-spin.

Cheers,
Bastian

  reply	other threads:[~2016-03-23  8:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-22 13:46 [Qemu-devel] [PULL 00/10] tricore-patches Bastian Koppelmann
2016-03-22 13:46 ` [Qemu-devel] [PULL 01/10] target-tricore: add missing break in insn decode switch stmt Bastian Koppelmann
2016-03-22 13:46 ` [Qemu-devel] [PULL 02/10] target-tricore: Fix helper_msub64_q_ssov not reseting OVF bit Bastian Koppelmann
2016-03-22 13:46 ` [Qemu-devel] [PULL 03/10] target-tricore: Fix psw_read() clearing too many bits Bastian Koppelmann
2016-03-22 13:46 ` [Qemu-devel] [PULL 04/10] target-tricore: Add FPU infrastructure Bastian Koppelmann
2016-03-22 13:46 ` [Qemu-devel] [PULL 05/10] target-tricore: Move general CHECK_REG_PAIR of decode_rrr_divide Bastian Koppelmann
2016-03-22 13:46 ` [Qemu-devel] [PULL 06/10] target-tricore: add add.f/sub.f instructions Bastian Koppelmann
2016-03-22 13:46 ` [Qemu-devel] [PULL 07/10] target-tricore: Add mul.f instruction Bastian Koppelmann
2016-03-22 13:46 ` [Qemu-devel] [PULL 08/10] target-tricore: Add div.f instruction Bastian Koppelmann
2016-03-22 13:46 ` [Qemu-devel] [PULL 09/10] target-tricore: Add cmp.f instruction Bastian Koppelmann
2016-03-22 13:46 ` [Qemu-devel] [PULL 10/10] target-tricore: Add ftoi and itof instructions Bastian Koppelmann
2016-03-22 20:15 ` [Qemu-devel] [PULL 00/10] tricore-patches Peter Maydell
2016-03-23  8:17   ` Bastian Koppelmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-05-22 15:05 Bastian Koppelmann
2015-05-22 16:19 ` 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=56F25137.5020807@mail.uni-paderborn.de \
    --to=kbastian@mail.uni-paderborn.de \
    --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).