On 27/03/15 11:46, Jan Beulich wrote:
On 27.03.15 at 12:14, wrote:
IIRC, MS ABI is supported starting from GCC v4.0.
Where did you find that? From all I know __attribute__((__ms_abi__))
is being supported only by 4.5 and newer. The mere support of the
MS ABI via command line option doesn't hel
>>> On 27.03.15 at 12:14, wrote:
> IIRC, MS ABI is supported starting from GCC v4.0.
Where did you find that? From all I know __attribute__((__ms_abi__))
is being supported only by 4.5 and newer. The mere support of the
MS ABI via command line option doesn't help us, as we need to be
able to mix
On Mon, Mar 02, 2015 at 04:14:22PM +, Jan Beulich wrote:
> >>> On 30.01.15 at 18:54, wrote:
> > --- a/xen/arch/x86/efi/Makefile
> > +++ b/xen/arch/x86/efi/Makefile
> > @@ -1,14 +1,14 @@
> > CFLAGS += -fshort-wchar
> >
> > -obj-y += stub.o
> > +obj-y += boot.o
> > +obj-y += compat.o
> > +obj-y
>>> On 30.01.15 at 18:54, wrote:
> --- a/xen/arch/x86/efi/Makefile
> +++ b/xen/arch/x86/efi/Makefile
> @@ -1,14 +1,14 @@
> CFLAGS += -fshort-wchar
>
> -obj-y += stub.o
> +obj-y += boot.o
> +obj-y += compat.o
> +obj-y += runtime.o
So how is this going to work with a compiler not new enough to
s
Build xen.gz with EFI code. We need this to support multiboot2
protocol on EFI platforms.
If we wish to load not ELF file using multiboot (v1) or multiboot2 then
it must contain "linear" (or "flat") representation of code and data.
Currently, PE file contains many sections which are not "linear" (
