qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: BALATON Zoltan <balaton@eik.bme.hu>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Palmer Dabbelt <palmer@sifive.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	Sagar Karandikar <sagark@eecs.berkeley.edu>,
	David Hildenbrand <david@redhat.com>,
	Bastian Koppelmann <kbastian@mail.uni-paderborn.de>,
	Cornelia Huck <cohuck@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Laurent Vivier <laurent@vivier.eu>,
	Max Filippov <jcmvbkbc@gmail.com>,
	Alistair Francis <alistair.francis@wdc.com>,
	Aleksandar Markovic <amarkovic@wavecomp.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
	Stefan Weil <sw@weilnetz.de>,
	"aurelien@aurel32.net" <aurelien@aurel32.net>,
	David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [EXTERNAL]Re: Proposal for amending TCG interface naming scheme
Date: Tue, 20 Aug 2019 18:21:05 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LMD.2.03.1908201811150.2980@eik.bme.hu> (raw)
In-Reply-To: <1fc18db5-abd4-80be-11ee-209dfd4a55f4@linaro.org>

Hello,

Sorry to comment on this without really knowing what is it about but maybe 
my view is not completely useless if this is to be understood by people 
who don't know anything about it. If it is not useful just ignore.

On Tue, 20 Aug 2019, Richard Henderson wrote:
> Would it be clearer to use the x86 instruction name: SHRD (SHift Right Doubleword)?

Not unless you name it shr32 or something like that. SHRD does not look 
meaningful without knowing the instruction and elsewhere you use bit 
numbers instead of b, w, d letters. (I don't know if shr32 is actually a 
good name for this op, just commenting on the naming itself.)

> What if we use the AArch64 mnemonics: zxt (zero-extend) and sxt (sign-extend)?
> This would give us
>
>    tcg_gen_zxt8_i32
>    tcg_gen_sxt8_i32
>    (etc)
>    tcg_gen_zxt_i32_i64
>    tcg_gen_sxt_i32_i64

Again this might look familiar to those knowing AArch64 but not to someone 
who does not know that. Maybe zext sext is a bit more decypherable.

In general I think it would be best to name these to describe what they do 
not necessarily following any other ISA naming because that's only useful 
for those who know those particular instructions so maybe it should be 
consistent within TCG and does not have to match what CPUs call it.

Regards,
BALATON Zoltan


  parent reply	other threads:[~2019-08-20 16:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-20 12:49 [Qemu-devel] Proposal for amending TCG interface naming scheme Aleksandar Markovic
2019-08-20 13:21 ` Peter Maydell
2019-08-20 13:49   ` [Qemu-devel] [EXTERNAL]Re: " Aleksandar Markovic
2019-08-20 15:37     ` Richard Henderson
2019-08-20 16:15       ` Aleksandar Markovic
2019-08-20 16:47         ` Richard Henderson
2019-08-20 16:21       ` BALATON Zoltan [this message]
2019-08-20 16:38         ` Aleksandar Markovic
2019-08-20 16:44           ` David Hildenbrand
2019-08-20 16:47             ` Peter Maydell
2019-08-20 17:57               ` Aleksandar Markovic
2019-08-20 16:48             ` Laurent Vivier
2019-08-20 16:52               ` Aleksandar Markovic
2019-08-20 17:02             ` Aleksandar Markovic
2019-08-20 18:08               ` David Hildenbrand
2019-08-21 16:29         ` Philippe Mathieu-Daudé
2019-08-20 16:46       ` David Hildenbrand
2019-08-21 16:15         ` Philippe Mathieu-Daudé
2019-09-09  9:10       ` Aleksandar Markovic

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=alpine.LMD.2.03.1908201811150.2980@eik.bme.hu \
    --to=balaton@eik.bme.hu \
    --cc=alistair.francis@wdc.com \
    --cc=amarkovic@wavecomp.com \
    --cc=aurelien@aurel32.net \
    --cc=cohuck@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=david@redhat.com \
    --cc=edgar.iglesias@gmail.com \
    --cc=ehabkost@redhat.com \
    --cc=jcmvbkbc@gmail.com \
    --cc=kbastian@mail.uni-paderborn.de \
    --cc=laurent@vivier.eu \
    --cc=palmer@sifive.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=sagark@eecs.berkeley.edu \
    --cc=sw@weilnetz.de \
    /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).