[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] dyngen-exec.h vs. qemu-common.h
From: |
Jan Kiszka |
Subject: |
[Qemu-devel] dyngen-exec.h vs. qemu-common.h |
Date: |
Fri, 05 Dec 2008 09:45:01 +0100 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 |
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
signature.asc
Description: OpenPGP digital signature
- [Qemu-devel] dyngen-exec.h vs. qemu-common.h,
Jan Kiszka <=