From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:40634)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <afaerber@suse.de>) id 1Utlvy-00035w-Rx
	for qemu-devel@nongnu.org; Mon, 01 Jul 2013 17:46:57 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <afaerber@suse.de>) id 1Utlvy-0001vS-3P
	for qemu-devel@nongnu.org; Mon, 01 Jul 2013 17:46:54 -0400
Received: from cantor2.suse.de ([195.135.220.15]:48264 helo=mx2.suse.de)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <afaerber@suse.de>) id 1Utlvx-0001vI-TN
	for qemu-devel@nongnu.org; Mon, 01 Jul 2013 17:46:54 -0400
Message-ID: <51D1F8C8.2020104@suse.de>
Date: Mon, 01 Jul 2013 23:46:48 +0200
From: =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= <afaerber@suse.de>
MIME-Version: 1.0
References: <1372536117-28167-1-git-send-email-afaerber@suse.de>
	<1372536117-28167-24-git-send-email-afaerber@suse.de>
	<51D1B98A.2010908@twiddle.net> <51D1C1AF.7080300@suse.de>
	<51D1C474.2000901@twiddle.net>
In-Reply-To: <51D1C474.2000901@twiddle.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] [PATCH RFC qom-cpu 23/41] target-xtensa: Change
 gen_intermediate_code_internal() arg to XtensaCPU
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: Richard Henderson <rth@twiddle.net>
Cc: Mike Frysinger <vapier@gentoo.org>, Max Filippov <jcmvbkbc@gmail.com>, jan.kiszka@web.de, qemu-devel@nongnu.org

Am 01.07.2013 20:03, schrieb Richard Henderson:
> On 07/01/2013 10:51 AM, Andreas F=C3=A4rber wrote:
>> I wonder, all targets seem to implement the same pattern of passing a
>> hard-coded bool argument to their internal function.
>>
>> Is there any reason not to have translate-all.c call the function with
>> that true/false directly?
>=20
> The idea is to avoid runtime checks for the rare search_pc case.
>=20
> Instead we pass constants to inline functions and transform what would =
be
> runtime checks into compile-time optimized code paths.

Thanks for the explanation!

Not every target seems to be aware of that, I'll put together a patch.

Andreas

--=20
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=C3=BCrnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imend=C3=B6rffer; HRB 16746 AG N=C3=BC=
rnberg