qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Bastian Koppelmann <kbastian@mail.uni-paderborn.de>
To: Richard Henderson <rth@twiddle.net>, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org
Subject: Re: [Qemu-devel] [PATCH v4 01/15] target-tricore: Add target stubs and qom-cpu
Date: Mon, 11 Aug 2014 17:06:45 +0100	[thread overview]
Message-ID: <53E8EA15.6050905@mail.uni-paderborn.de> (raw)
In-Reply-To: <53E435EA.3070408@twiddle.net>


On 08/08/2014 03:28 AM, Richard Henderson wrote:
> On 08/07/2014 04:34 AM, Bastian Koppelmann wrote:
>> +    /* PSW flag cache for faster execution
>> +       if flag != 0 then flag is set. Else flag is not set.
>> +    */
>> +    target_ulong PSW_USB_C;
>> +    target_ulong PSW_USB_V;
>> +    target_ulong PSW_USB_SV;
>> +    target_ulong PSW_USB_AV;  /* Only if bit 31 set, then flag is set. */
>> +    target_ulong PSW_USB_SAV; /* Only if bit 31 set, then flag is set. */
> V and SV are also only set if bit 31 is set, the way we're computing overflow
> from addition.  Of course, overflow from saturation or multiplication isn't
> being computed into bit 31, so there is a decision to make.
>
> Depending on how important it is for ADDX+ADDC to be implemented efficiently,
> vs how important is for SHA to be quick, you may wish to have C already set to
> 0/1 only.

Since I don't have data, which instructions are more common, I would 
choose the SHA instructions to be fast, because the manual states, that 
the most commen instructions are also implemented as 16 bit instructions 
and SHA is part of those. So I would leave the carry bit as is, unless 
you are sure, that there is a benefit for ADDX+ADDC to be fast.

>
>
> r~

  parent reply	other threads:[~2014-08-11 15:03 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-07 14:34 [Qemu-devel] [PATCH v4 00/15] TriCore architecture guest implementation Bastian Koppelmann
2014-08-07 14:34 ` [Qemu-devel] [PATCH v4 01/15] target-tricore: Add target stubs and qom-cpu Bastian Koppelmann
2014-08-08  2:28   ` Richard Henderson
2014-08-08 10:40     ` Bastian Koppelmann
2014-08-08 11:35       ` Bastian Koppelmann
2014-08-11 16:06     ` Bastian Koppelmann [this message]
2014-08-07 14:34 ` [Qemu-devel] [PATCH v4 02/15] target-tricore: Add board for systemmode Bastian Koppelmann
2014-08-07 14:34 ` [Qemu-devel] [PATCH v4 03/15] target-tricore: Add softmmu support Bastian Koppelmann
2014-08-07 14:34 ` [Qemu-devel] [PATCH v4 04/15] target-tricore: Add initialization for translation and activate target Bastian Koppelmann
2014-08-07 14:34 ` [Qemu-devel] [PATCH v4 05/15] target-tricore: Add masks and opcodes for decoding Bastian Koppelmann
2014-08-07 14:34 ` [Qemu-devel] [PATCH v4 06/15] target-tricore: Add instructions of SRC opcode format Bastian Koppelmann
2014-08-08  2:58   ` Richard Henderson
2014-08-07 14:34 ` [Qemu-devel] [PATCH v4 07/15] target-tricore: Add instructions of SRR " Bastian Koppelmann
2014-08-07 14:34 ` [Qemu-devel] [PATCH v4 08/15] target-tricore: Add instructions of SSR " Bastian Koppelmann
2014-08-07 14:34 ` [Qemu-devel] [PATCH v4 09/15] target-tricore: Add instructions of SRRS and SLRO " Bastian Koppelmann
2014-08-07 14:34 ` [Qemu-devel] [PATCH v4 10/15] target-tricore: Add instructions of SB " Bastian Koppelmann
2014-08-07 14:34 ` [Qemu-devel] [PATCH v4 11/15] target-tricore: Add instructions of SBC and SBRN " Bastian Koppelmann
2014-08-07 14:34 ` [Qemu-devel] [PATCH v4 12/15] target-tricore: Add instructions of SBR " Bastian Koppelmann
2014-08-07 14:34 ` [Qemu-devel] [PATCH v4 13/15] target-tricore: Add instructions of SC " Bastian Koppelmann
2014-08-07 14:34 ` [Qemu-devel] [PATCH v4 14/15] target-tricore: Add instructions of SLR, SSRO and SRO " Bastian Koppelmann
2014-08-07 14:34 ` [Qemu-devel] [PATCH v4 15/15] target-tricore: Add instructions of SR " Bastian Koppelmann

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=53E8EA15.6050905@mail.uni-paderborn.de \
    --to=kbastian@mail.uni-paderborn.de \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@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 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).