>>> On 20.01.15 at 15:00, <andrew.coop...@citrix.com> wrote: > On 20/01/15 13:48, Jan Beulich wrote: >>>>> On 20.01.15 at 14:39, <andrew.coop...@citrix.com> wrote: >>> It is far nicer to work from a document than to worry how another >>> compiler might change the structure. >> Compilers have (almost, i.e. leaving aside bitfields) no freedom in laying >> out structures - any platform's ABI defines how this needs to be done. >> Or else code compiled with different compilers wouldn't inter-operate. > > Widths of types are not consistent.
Hence the need to use fixed-width ones (and explicit padding). > Attempting to use the Xen header files on windows requires sed because > unsigned longs are still 32 bits even on 64bit windows. (i.e. an > unsigned long is not valid for a pointer of natural width, which occurs > even in the HVM ABI). I think we made quite a bit of progress eliminating the uses of "long" in the public headers. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
