From: Richard Henderson <richard.henderson@linaro.org>
To: David Hildenbrand <david@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-s390x@nongnu.org, Cornelia Huck <cohuck@redhat.com>,
Thomas Huth <thuth@redhat.com>
Subject: Re: [PATCH v1 6/8] s390x/tcg: Implement MULTIPLY SINGLE (MSC, MSGC, MSGRKC, MSRKC)
Date: Fri, 25 Sep 2020 15:06:28 -0700 [thread overview]
Message-ID: <371cb429-a7e2-819e-a016-08bd7adff54e@linaro.org> (raw)
In-Reply-To: <20200922103129.12824-7-david@redhat.com>
On 9/22/20 3:31 AM, David Hildenbrand wrote:
> +static uint32_t cc_calc_muls_32(int64_t res)
> +{
> + /* Arithmetic shift with sign extension so we can compare against -1ull. */
> + const uint64_t tmp = res >> 31;
> +
> + if (!res) {
> + return 0;
> + } else if (!(!tmp || tmp == -1ull)) {
Comparing signed vs unsigned. Use -1 without suffix.
> +static uint64_t cc_calc_muls_64(int64_t res_high, uint64_t res_low)
> +{
> + const uint8_t tmp = res_low >> 63;
> +
> + if (!res_high && !res_low) {
> + return 0;
> + } else if (!(!res_high && !tmp) || !(res_high == -1ull && tmp)) {
This simplifies to res_high + tmp != 0.
Probably better to keep tmp as uint64_t; otherwise we're likely to have an
unnecessary zero-extension from uint8_t to uint64_t.
Or, drop 'tmp' altogether and use
if (res_high + (res_low >> 63) != 0)
Otherwise, looks good.
r~
next prev parent reply other threads:[~2020-09-25 22:08 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 10:31 [PATCH v1 0/8] s390x/tcg: Implement some z14 facilities David Hildenbrand
2020-09-22 10:31 ` [PATCH v1 1/8] s390x/tcg: Implement ADD HALFWORD (AGH) David Hildenbrand
2020-09-23 4:49 ` Thomas Huth
2020-09-23 4:53 ` Thomas Huth
2020-09-23 7:50 ` David Hildenbrand
2020-09-25 21:25 ` Richard Henderson
2020-09-22 10:31 ` [PATCH v1 2/8] s390x/tcg: Implement SUBTRACT HALFWORD (SGH) David Hildenbrand
2020-09-23 4:52 ` Thomas Huth
2020-09-25 21:25 ` Richard Henderson
2020-09-22 10:31 ` [PATCH v1 3/8] s390x/tcg: Implement MULTIPLY (MG, MGRK) David Hildenbrand
2020-09-25 21:36 ` Richard Henderson
2020-09-22 10:31 ` [PATCH v1 4/8] s390x/tcg: Implement MULTIPLY HALFWORD (MGH) David Hildenbrand
2020-09-25 21:39 ` Richard Henderson
2020-09-22 10:31 ` [PATCH v1 5/8] s390x/tcg: Implement BRANCH INDIRECT ON CONDITION (BIC) David Hildenbrand
2020-09-25 21:45 ` Richard Henderson
2020-09-28 11:50 ` David Hildenbrand
2020-09-22 10:31 ` [PATCH v1 6/8] s390x/tcg: Implement MULTIPLY SINGLE (MSC, MSGC, MSGRKC, MSRKC) David Hildenbrand
2020-09-22 16:14 ` Richard Henderson
2020-09-22 16:19 ` David Hildenbrand
2020-09-25 22:06 ` Richard Henderson [this message]
2020-09-28 12:13 ` David Hildenbrand
2020-09-22 10:31 ` [PATCH v1 7/8] s390x/tcg: We support Miscellaneous-Instruction-Extensions Facility 2 David Hildenbrand
2020-09-25 22:08 ` Richard Henderson
2020-09-22 10:31 ` [PATCH v1 8/8] s390x/tcg: Implement CIPHER MESSAGE WITH AUTHENTICATION (KMA) David Hildenbrand
2020-09-25 22:12 ` Richard Henderson
2020-09-22 15:41 ` [PATCH v1 0/8] s390x/tcg: Implement some z14 facilities no-reply
2020-09-25 22:43 ` Richard Henderson
2020-09-28 11:54 ` David Hildenbrand
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=371cb429-a7e2-819e-a016-08bd7adff54e@linaro.org \
--to=richard.henderson@linaro.org \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=thuth@redhat.com \
/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).