[Qemu-devel] dyngen-exec.h vs. qemu-common.h

[Jan Kiszka <jan.kiszka@web.de>]

[-- Attachment #1: Type: text/plain, Size: 817 bytes --]

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


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]