From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:43314)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <afaerber@suse.de>) id 1WDbh8-0003hO-1N
	for qemu-devel@nongnu.org; Wed, 12 Feb 2014 10:25:57 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <afaerber@suse.de>) id 1WDbh0-0006cn-J5
	for qemu-devel@nongnu.org; Wed, 12 Feb 2014 10:25:49 -0500
Received: from cantor2.suse.de ([195.135.220.15]:35210 helo=mx2.suse.de)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <afaerber@suse.de>) id 1WDbgz-0006ch-W2
	for qemu-devel@nongnu.org; Wed, 12 Feb 2014 10:25:42 -0500
Message-ID: <52FB9273.5080907@suse.de>
Date: Wed, 12 Feb 2014 16:25:39 +0100
From: =?ISO-8859-15?Q?Andreas_F=E4rber?= <afaerber@suse.de>
MIME-Version: 1.0
References: <1392132687-18664-1-git-send-email-peter.maydell@linaro.org>
In-Reply-To: <1392132687-18664-1-git-send-email-peter.maydell@linaro.org>
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] [RFC] translate-all.c: add hack for coverage
	testing
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: patches@linaro.org, Richard Henderson <rth@twiddle.net>

Am 11.02.2014 16:31, schrieb Peter Maydell:
> Actually this barely even rises to the level of an RFC, but
> since I'm not entirely sure how or if it might be possible to
> turn this into upstreamable code I thought I might as well
> send it out as-is in case anybody else finds it useful.
>=20
> The basic idea is that you build the linux-user binary and
> run it on something (anything). Instead of actually running
> code we instead just loop round feeding every possible
> instruction pattern to the decoder. This lets us catch:
>  * "can't happen" assertions in the wrong place
>  * TCG temp leaks
>  * insns which generate too many TCG ops
>=20
> Obvious deficiencies here:
>  * no UI for specifying that you want to test a smaller
>    part of the instruction space
>  * an assumption that instructions are fixed-length 32 bits
>  * cheesily hardwired in

Wasn't there a previous proposal to do an accel=3Dtcgtest? That would be
the way I'd expect such test frameworks to be dynamically invoked.

Regards,
Andreas

--=20
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=FCrnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imend=F6rffer; HRB 16746 AG N=FCrnbe=
rg