On Thu, 2013-02-14 at 10:25 -0800, Andrew Fish wrote: > > This issue is not an ANSI C memory model conformance issue. It is an > artifact of the set of C ABIs that UEFI supports. > For example the default alignment for UINT64 on gcc is 32-bit, while > in UEFI /Visual Studio it is 64-bit.
Well yes, one does kind of hope that one's compiler will actually get the ABI correct. If you use GCC on x86_64 *without* explicitly asking it to use the Microsoft ABI, you'll also get all your function arguments in the wrong registers... which doesn't work very well either. . > > Of course, in this particular case it probably serves us right for using > > this UTF-16 abomination instead of UTF-8... but that's a different > > story :) > > We outsourced that choice a long time ago to experts. You can guess > which camp they were in.... :( -- dwmw2
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________ edk2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel
