qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Bastian Koppelmann <kbastian@mail.uni-paderborn.de>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 0/9] tricore patches
Date: Tue, 27 Jan 2015 10:40:22 +0000	[thread overview]
Message-ID: <CAFEAcA8UVNTeevOVkmt_tWdhvZi6_yJ30FVREdanzpOw_XgDCg@mail.gmail.com> (raw)
In-Reply-To: <1422302600-21514-1-git-send-email-kbastian@mail.uni-paderborn.de>

On 26 January 2015 at 20:03, Bastian Koppelmann
<kbastian@mail.uni-paderborn.de> wrote:
> The following changes since commit 1ac0206b2ae1ffaeec564f110664a3a77bafafd2:
>
>   qemu-timer.c: Trim list of included headers (2015-01-26 18:15:54 +0000)
>
> are available in the git repository at:
>
>   https://github.com/bkoppelmann/qemu-tricore-upstream.git tags/pull-tricore20150126-2
>
> for you to fetch changes up to 24c3bf03341ada63a0728f2bdfd2b7c226ad958e:
>
>   target-tricore: Add instructions of RRR opcode format (2015-01-26 19:56:46 +0000)
>
> ----------------------------------------------------------------
> tricore bugfixes and RR1, RR2, RRPW and RRR insn
>
> ----------------------------------------------------------------

Looks like this would introduce a new clang warning:

/home/petmay01/linaro/qemu-for-merges/target-tricore/translate.c:1049:23:
warning: equality
      comparison with extraneous parentheses [-Wparentheses-equality]
        if ((up_shift == 32)) {
             ~~~~~~~~~^~~~~
/home/petmay01/linaro/qemu-for-merges/target-tricore/translate.c:1049:23:
note: remove extraneous
      parentheses around the comparison to silence this warning
        if ((up_shift == 32)) {
            ~         ^    ~
/home/petmay01/linaro/qemu-for-merges/target-tricore/translate.c:1049:23:
note: use '=' to turn
      this equality comparison into an assignment
        if ((up_shift == 32)) {
                      ^~
                      =

We've nearly managed to eradicate all our clang warnings so I
don't want to add more at this point -- could you fix this
and resend the pullreq, please?

thanks
-- PMM

  parent reply	other threads:[~2015-01-27 10:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-26 20:03 [Qemu-devel] [PULL 0/9] tricore patches Bastian Koppelmann
2015-01-26 20:03 ` [Qemu-devel] [PULL 1/9] target-tricore: Add missing ULL suffix on 64 bit constant Bastian Koppelmann
2015-01-26 20:03 ` [Qemu-devel] [PULL 2/9] target-tricore: Several translator and cpu model fixes Bastian Koppelmann
2015-01-26 20:03 ` [Qemu-devel] [PULL 3/9] target-tricore: calculate av bits before saturation Bastian Koppelmann
2015-01-26 20:03 ` [Qemu-devel] [PULL 4/9] target-tricore: Fix bugs found by coverity Bastian Koppelmann
2015-01-26 20:03 ` [Qemu-devel] [PULL 5/9] target-tricore: split up suov32 into suov32_pos and suov32_neg Bastian Koppelmann
2015-01-26 20:03 ` [Qemu-devel] [PULL 6/9] target-tricore: target-tricore: Add instructions of RR1 opcode format, that have 0x93 as first opcode Bastian Koppelmann
2015-01-26 20:03 ` [Qemu-devel] [PULL 7/9] target-tricore: Add instructions of RR2 opcode format Bastian Koppelmann
2015-01-26 20:03 ` [Qemu-devel] [PULL 8/9] target-tricore: Add instructions of RRPW " Bastian Koppelmann
2015-01-26 20:03 ` [Qemu-devel] [PULL 9/9] target-tricore: Add instructions of RRR " Bastian Koppelmann
2015-01-27 10:40 ` Peter Maydell [this message]
2015-01-27 11:45   ` [Qemu-devel] [PULL 0/9] tricore patches Bastian Koppelmann
2015-01-27 11:23     ` Peter Maydell
  -- strict thread matches above, loose matches on Subject: below --
2014-12-10 11:36 Bastian Koppelmann
2014-12-11 12:07 ` 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=CAFEAcA8UVNTeevOVkmt_tWdhvZi6_yJ30FVREdanzpOw_XgDCg@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=kbastian@mail.uni-paderborn.de \
    --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).