From: Jeff Law <law@redhat.com>
To: Helge Deller <deller@gmx.de>, Richard Henderson <rth@twiddle.net>
Cc: linux-parisc@vger.kernel.org, GNU C Library <libc-alpha@sourceware.org>
Subject: Re: Aw: hppa qemu and string functions
Date: Wed, 09 Nov 2016 15:51:00 -0000 [thread overview]
Message-ID: <32965c22-66ed-3012-a392-5a8aba28aa12@redhat.com> (raw)
In-Reply-To: <trinity-8a5a9da3-1e08-4571-bbfb-b230bd20f15b-1478703076818@3capp-gmx-bs52>
On 11/09/2016 07:51 AM, Helge Deller wrote:
> Hi Richard,
>
>> Off and on, I've been working on a user-only target of hppa to qemu. It's now
>> about 95% working. If anyone would like to try it out, it's available at
>> git://github.com/rth7680/qemu.git tgt-hppa
>
> COOL!
> I'm happy to test, but can you shortly describe the required steps how I can build & test it?
>
> With "user-only target of hppa" I assume this means that I can run hppa binaries
> on e.g. x86-64, similiar to what is described here: https://wiki.debian.org/QemuUserEmulation ?
>
>> While implementing the unit-type instructions, I wondered why no one (outside
>> hp?) had written a version of the string routines utilizing the UXOR insn, with
>> the SomeByteZero and NoByteZero conditions.
>
> Interesting.
> I assume nobody did, because there are a few hppa/linux/glibc users anyway ? :-)
Probably a safe assumption. I'm pretty sure the hpux string routines
used uxor. There was also at least one hpux routine in libc which used
the branch-in-delay-slot-of-branch trick, but I can't recall why it was
useful.
jeff
next prev parent reply other threads:[~2016-11-09 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 12:53 Richard Henderson
2016-11-09 14:51 ` Aw: " Helge Deller
2016-11-09 15:51 ` Jeff Law [this message]
2016-11-10 9:39 ` Richard Henderson
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=32965c22-66ed-3012-a392-5a8aba28aa12@redhat.com \
--to=law@redhat.com \
--cc=deller@gmx.de \
--cc=libc-alpha@sourceware.org \
--cc=linux-parisc@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).