public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "Helge Deller" <deller@gmx.de>
To: "Richard Henderson" <rth@twiddle.net>
Cc: linux-parisc@vger.kernel.org,
	"GNU C Library" <libc-alpha@sourceware.org>
Subject: Aw: hppa qemu and string functions
Date: Wed, 09 Nov 2016 14:51:00 -0000	[thread overview]
Message-ID: <trinity-8a5a9da3-1e08-4571-bbfb-b230bd20f15b-1478703076818@3capp-gmx-bs52> (raw)
In-Reply-To: <21645bc2-f005-5e60-d26a-41af60e3c035@twiddle.net>

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 ? :-)
 
> Attached are versions of strlen, strchr and strrchr.  They pass simple tests 
> within my emulator; I'd be interested to know if they pass full glibc testing 
> on real hardware.

If you like I can give you access to a hppa-linux box...

Helge

  reply	other threads:[~2016-11-09 14: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 ` Helge Deller [this message]
2016-11-09 15:51   ` Aw: " Jeff Law
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=trinity-8a5a9da3-1e08-4571-bbfb-b230bd20f15b-1478703076818@3capp-gmx-bs52 \
    --to=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).