From: Richard Henderson <richard.henderson@linaro.org>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
BALATON Zoltan <balaton@eik.bme.hu>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org, david@gibson.dropbear.id.au
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH v3 2/8] target/ppc: rework vmrg{l, h}{b, h, w} instructions to use Vsr* macros
Date: Sun, 27 Jan 2019 09:26:02 -0800 [thread overview]
Message-ID: <5ea37d08-91f6-33cc-b220-f1a96796d794@linaro.org> (raw)
In-Reply-To: <3dc12858-4254-9da1-7eb2-309948d0d376@ilande.co.uk>
On 1/27/19 7:19 AM, Mark Cave-Ayland wrote:
> Could this make the loop slower? I certainly haven't noticed any obvious
> performance difference during testing (OS X uses merge quite a bit for
> display rendering), and I'd hope that with a good compiler and modern branch
> prediction then any effect here would be negligible.
I would expect the i < n/2 loop to be faster, because the assignments are
unconditional. FWIW.
r~
next prev parent reply other threads:[~2019-01-27 17:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-27 9:02 [Qemu-devel] [PATCH v3 0/8] target/ppc: remove various endian hacks from int_helper.c Mark Cave-Ayland
2019-01-27 9:02 ` [Qemu-devel] [PATCH v3 1/8] target/ppc: implement complete set of Vsr* macros Mark Cave-Ayland
2019-01-28 9:19 ` David Gibson
2019-01-27 9:03 ` [Qemu-devel] [PATCH v3 2/8] target/ppc: rework vmrg{l, h}{b, h, w} instructions to use " Mark Cave-Ayland
2019-01-27 12:07 ` [Qemu-devel] [Qemu-ppc] " BALATON Zoltan
2019-01-27 15:19 ` Mark Cave-Ayland
2019-01-27 17:26 ` Richard Henderson [this message]
2019-01-27 17:45 ` Mark Cave-Ayland
2019-01-27 18:07 ` Richard Henderson
2019-01-29 2:28 ` David Gibson
2019-01-29 6:36 ` Mark Cave-Ayland
2019-01-29 18:49 ` Mark Cave-Ayland
2019-01-27 20:31 ` BALATON Zoltan
2019-01-27 20:47 ` BALATON Zoltan
2019-01-27 9:03 ` [Qemu-devel] [PATCH v3 3/8] target/ppc: rework vmul{e, o}{s, u}{b, " Mark Cave-Ayland
2019-01-27 9:03 ` [Qemu-devel] [PATCH v3 4/8] target/ppc: eliminate use of HI_IDX and LO_IDX macros from int_helper.c Mark Cave-Ayland
2019-01-27 19:13 ` Richard Henderson
2019-01-27 9:03 ` [Qemu-devel] [PATCH v3 5/8] target/ppc: eliminate use of EL_IDX " Mark Cave-Ayland
2019-01-27 9:03 ` [Qemu-devel] [PATCH v3 6/8] target/ppc: simplify VEXT_SIGNED macro in int_helper.c Mark Cave-Ayland
2019-01-27 9:03 ` [Qemu-devel] [PATCH v3 7/8] target/ppc: remove ROTRu32 and ROTRu64 macros from int_helper.c Mark Cave-Ayland
2019-01-27 9:03 ` [Qemu-devel] [PATCH v3 8/8] target/ppc: remove various HOST_WORDS_BIGENDIAN hacks in int_helper.c Mark Cave-Ayland
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=5ea37d08-91f6-33cc-b220-f1a96796d794@linaro.org \
--to=richard.henderson@linaro.org \
--cc=balaton@eik.bme.hu \
--cc=david@gibson.dropbear.id.au \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).