From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1L8WJI-0007wf-N2 for qemu-devel@nongnu.org; Fri, 05 Dec 2008 03:45:16 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1L8WJG-0007vs-Sk for qemu-devel@nongnu.org; Fri, 05 Dec 2008 03:45:16 -0500 Received: from [199.232.76.173] (port=43928 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L8WJG-0007vk-K5 for qemu-devel@nongnu.org; Fri, 05 Dec 2008 03:45:14 -0500 Received: from fmmailgate03.web.de ([217.72.192.234]:55395) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1L8WJG-0007D7-2e for qemu-devel@nongnu.org; Fri, 05 Dec 2008 03:45:14 -0500 Received: from smtp05.web.de (fmsmtp05.dlan.cinetic.de [172.20.4.166]) by fmmailgate03.web.de (Postfix) with ESMTP id 8B14AF52117C for ; Fri, 5 Dec 2008 09:45:12 +0100 (CET) Received: from [88.64.13.18] (helo=[192.168.1.198]) by smtp05.web.de with asmtp (TLSv1:AES256-SHA:256) (WEB.DE 4.109 #226) id 1L8WJE-0005gI-00 for qemu-devel@nongnu.org; Fri, 05 Dec 2008 09:45:12 +0100 Message-ID: <4938EA0D.7010004@web.de> Date: Fri, 05 Dec 2008 09:45:01 +0100 From: Jan Kiszka MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig97BC3602DFF0E8A6D1D5D5D3" Sender: jan.kiszka@web.de Subject: [Qemu-devel] 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) --------------enig97BC3602DFF0E8A6D1D5D5D3 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Hi, 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 [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. */ 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. if 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? Thanks, Jan --------------enig97BC3602DFF0E8A6D1D5D5D3 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 iEYEARECAAYFAkk46hIACgkQniDOoMHTA+k04ACffGQw/7eivyTmOzSqQXm2z3VW z9oAmwUFO5VJySKssLhidpqvVjyKJtYn =IWGV -----END PGP SIGNATURE----- --------------enig97BC3602DFF0E8A6D1D5D5D3--