From: Richard Henderson <rth@twiddle.net>
To: Stefan Weil <sw@weilnetz.de>,
Peter Hanzel <hanzelpeter@gmail.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Raspbian in QEMU
Date: Wed, 12 Mar 2014 12:41:15 -0700 [thread overview]
Message-ID: <5320B85B.4030202@twiddle.net> (raw)
In-Reply-To: <5320ADCF.5000406@weilnetz.de>
On 03/12/2014 11:56 AM, Stefan Weil wrote:
> Am 12.03.2014 19:05, schrieb Peter Hanzel:
>> Thanks.
>>
>> Now it makes sense. Also google now works and led me to
>> https://github.com/bavison/arm-mem.
>> And there is SETEND used.
>>
>
> It might be possible to handle that special case in QEMU without
> implementing setend:
>
> That instruction is only used in the implementation of function memcmp.
> When TCG detects a setend instruction, it could check whether the
> surrounding code has the signature of that memcmp implementation and add
> code which calls a memcmp helper function. The setend instruction and
> all the following code of memcmp would be handled as if it were a single
> special multi byte machine instruction.
Ew. No. It would be easier to just implement setend, even if badly.
> PS. Link to previous discussion on setend:
> https://lists.gnu.org/archive/html/qemu-trivial/2013-08/msg00086.html
> I cc Richard because he was / is involved, too.
For my part, the endian-aware load/store opcodes I alluded to last
August are now in.
r~
next prev parent reply other threads:[~2014-03-12 19:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-12 9:55 [Qemu-devel] Raspbian in QEMU Peter Hanzel
2014-03-12 15:43 ` Peter Maydell
2014-03-12 18:05 ` Peter Hanzel
2014-03-12 18:56 ` Stefan Weil
2014-03-12 19:41 ` Richard Henderson [this message]
2014-03-12 20:01 ` Peter Maydell
2014-03-20 12:36 ` Paolo Bonzini
2014-03-20 13:08 ` François Revol
2014-03-20 13:21 ` Paolo Bonzini
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=5320B85B.4030202@twiddle.net \
--to=rth@twiddle.net \
--cc=hanzelpeter@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--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 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.