From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LBQqn-0001Sw-An for qemu-devel@nongnu.org; Sat, 13 Dec 2008 04:31:53 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LBQqk-0001QE-VH for qemu-devel@nongnu.org; Sat, 13 Dec 2008 04:31:51 -0500 Received: from [199.232.76.173] (port=37159 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LBQqk-0001Q6-Pb for qemu-devel@nongnu.org; Sat, 13 Dec 2008 04:31:50 -0500 Received: from fmmailgate02.web.de ([217.72.192.227]:36686) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LBQqk-0008SP-6s for qemu-devel@nongnu.org; Sat, 13 Dec 2008 04:31:50 -0500 Received: from smtp05.web.de (fmsmtp05.dlan.cinetic.de [172.20.4.166]) by fmmailgate02.web.de (Postfix) with ESMTP id 0F7C1F7A3310 for ; Sat, 13 Dec 2008 10:31:49 +0100 (CET) Received: from [88.64.11.10] (helo=[192.168.1.198]) by smtp05.web.de with asmtp (TLSv1:AES256-SHA:256) (WEB.DE 4.109 #226) id 1LBQqi-0003eg-00 for qemu-devel@nongnu.org; Sat, 13 Dec 2008 10:31:48 +0100 Message-ID: <494380EA.6030506@web.de> Date: Sat, 13 Dec 2008 10:31:22 +0100 From: Jan Kiszka MIME-Version: 1.0 References: <4938EA0D.7010004@web.de> In-Reply-To: <4938EA0D.7010004@web.de> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig31627EA8C1BB2A9C2D0D8149" Sender: jan.kiszka@web.de Subject: [Qemu-devel] Re: dyngen-exec.h vs. qemu-common.h Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig31627EA8C1BB2A9C2D0D8149 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Jan Kiszka wrote: > Hi, >=20 > right now dyngen-exec.h prevents that qemu-common.h (or other headers > that drag in standard headers) can be included into all parts of qemu. > The reason for this is that dyngen-exec.h redefines a bunch of standard= > types, and that is likely due to >=20 > [dyngen-exec.h:] > /* NOTE: standard headers should be used with special care at this > point because host CPU registers are used as global variables. Some > host headers do not allow that. */ >=20 > Trying to add the noreturn definition to a central place, I wonder now > if that comment will still be valid when we only have TCG archs, i.e. i= f > the successor of dyngen-exec.h could possibly become compatible with > standard headers? Or what host headers on what host OS / distro are the= > precise problem that could survive the dyngen era? >=20 Mmm, no one here who understands this code? Jan --------------enig31627EA8C1BB2A9C2D0D8149 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAklDgOoACgkQniDOoMHTA+mweQCeKqpWsjiwzbjySrXA/bKocbW7 LMcAnii2Gl/veSaTEa7j3M4QR8Qzy1PP =3I5J -----END PGP SIGNATURE----- --------------enig31627EA8C1BB2A9C2D0D8149--