All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: Bastian Koppelmann <kbastian@mail.uni-paderborn.de>,
	qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org
Subject: Re: [Qemu-devel] [PATCH 3/5] target-tricore: Add instructions of BRN opcode format
Date: Wed, 29 Oct 2014 18:56:34 -0700	[thread overview]
Message-ID: <54519AD2.1080608@twiddle.net> (raw)
In-Reply-To: <1414588941-845-4-git-send-email-kbastian@mail.uni-paderborn.de>

On 10/29/2014 06:22 AM, Bastian Koppelmann wrote:
> +        if (MASK_OP_BRN_OP2(ctx->opcode) == OPC2_32_BRN_JNZ_T) {
> +            tcg_gen_brcondi_tl(TCG_COND_NE, temp, 0, l1);
> +        } else {
> +            tcg_gen_brcondi_tl(TCG_COND_EQ, temp, 0, l1);
> +        }
> +        gen_goto_tb(ctx, 0, ctx->next_pc);
> +        gen_set_label(l1);
> +        gen_goto_tb(ctx, 1, ctx->pc + offset * 2);

This looks like gen_branch_condi.



r~

  reply	other threads:[~2014-10-30  1:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-29 13:22 [Qemu-devel] [PATCH 0/5] Add TriCore BOL, BRC, BRN, BRR and RC instructions Bastian Koppelmann
2014-10-29 13:22 ` [Qemu-devel] [PATCH 1/5] target-tricore: Add instructions of BOL opcode format Bastian Koppelmann
2014-10-30  1:20   ` Richard Henderson
2014-10-30  1:21   ` Richard Henderson
2014-10-29 13:22 ` [Qemu-devel] [PATCH 2/5] target-tricore: Add instructions of BRC " Bastian Koppelmann
2014-10-30  1:32   ` Richard Henderson
2014-10-29 13:22 ` [Qemu-devel] [PATCH 3/5] target-tricore: Add instructions of BRN " Bastian Koppelmann
2014-10-30  1:56   ` Richard Henderson [this message]
2014-10-29 13:22 ` [Qemu-devel] [PATCH 4/5] target-tricore: Add instructions of BRR " Bastian Koppelmann
2014-10-30  2:30   ` Richard Henderson
2014-10-29 13:22 ` [Qemu-devel] [PATCH 5/5] target-tricore: Add instructions of RC " Bastian Koppelmann
2014-10-30  2:56   ` Richard Henderson

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=54519AD2.1080608@twiddle.net \
    --to=rth@twiddle.net \
    --cc=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 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.