Xen devel - May 2005 - x86_64/entry.S:317: Error: `1(%eax)'' is not a valid 64 bit base/index

Using the May 17 xen-unstable-src.tgz on x86_64, the following error
occurs on a SLES 9 SP1 platform (It builds OK on Fedora Core 4, but it
does not boot, and that is another issue):				

gcc -nostdinc -fno-builtin -fno-common -fno-strict-aliasing -iwithprefix include
-Wall -Werror -Wno-pointer-arith -pipe -I/tmp/xen-unstable/xen/include
-I/tmp/xen-unstable/xen/include/asm-x86/mach-default -O3 -fomit-frame-pointer
-msoft-float -m64 -mno-red-zone -fpic -fno-reorder-blocks
-fno-asynchronous-unwind-tables -DNDEBUG -D__ASSEMBLY__ -c x86_64/entry.S -o
x86_64/entry.o
x86_64/entry.S: Assembler messages:
x86_64/entry.S:317: Error: `1(%eax)'' is not a valid 64 bit base/index
expressionx86_64/entry.S:320: Error: `136+8(%esp)'' is not a valid 64
bit
base/index expression
make[3]: *** [x86_64/entry.o] Error 1
make[3]: Leaving directory `/tmp/xen-unstable/xen/arch/x86''
make[2]: *** [/tmp/xen-unstable/xen/xen] Error 2
make[2]: Leaving directory `/tmp/xen-unstable/xen''
make[1]: *** [xen] Error 2
make[1]: Leaving directory `/tmp/xen-unstable''
make: *** [world] Error 2

-- 
Regards,

David F Barrera
Linux Technology Center
Systems and Technology Group, IBM

"The wisest men follow their own direction. "
                                                        Euripides


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On Wed, May 18, 2005 at 10:59:00AM -0500, David F Barrera
wrote:
> Using the May 17 xen-unstable-src.tgz on x86_64, the following error
> occurs on a SLES 9 SP1 platform (It builds OK on Fedora Core 4, but it
> does not boot, and that is another issue):				
> 
> gcc -nostdinc -fno-builtin -fno-common -fno-strict-aliasing -iwithprefix
include
> -Wall -Werror -Wno-pointer-arith -pipe -I/tmp/xen-unstable/xen/include
> -I/tmp/xen-unstable/xen/include/asm-x86/mach-default -O3
-fomit-frame-pointer
> -msoft-float -m64 -mno-red-zone -fpic -fno-reorder-blocks
> -fno-asynchronous-unwind-tables -DNDEBUG -D__ASSEMBLY__ -c x86_64/entry.S
-o
> x86_64/entry.o
> x86_64/entry.S: Assembler messages:
> x86_64/entry.S:317: Error: `1(%eax)'' is not a valid 64 bit
base/index
> expressionx86_64/entry.S:320: Error: `136+8(%esp)'' is not a valid
64 bit
> base/index expression
that''s odd. could you verify you have the correct line on entry.S ?

line 317: setnz VCPUINFO_upcall_mask(%rax)
line 320: movw  UREGS_cs+8(%rsp),%ax

as well, what compiler version are you using ?

-- 
Vincent Hanquez

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

The fix for this is in bitkeeper now. It did not make it into the
unstable tar ball for the night. So you will not see this problem
tommorow.

On 5/18/05, Vincent Hanquez <vincent.hanquez@cl.cam.ac.uk>
wrote:
> On Wed, May 18, 2005 at 10:59:00AM -0500, David F Barrera wrote:
> > Using the May 17 xen-unstable-src.tgz on x86_64, the following error
> > occurs on a SLES 9 SP1 platform (It builds OK on Fedora Core 4, but it
> > does not boot, and that is another issue):
> >
> > gcc -nostdinc -fno-builtin -fno-common -fno-strict-aliasing
-iwithprefix include
> > -Wall -Werror -Wno-pointer-arith -pipe -I/tmp/xen-unstable/xen/include
> > -I/tmp/xen-unstable/xen/include/asm-x86/mach-default -O3
-fomit-frame-pointer
> > -msoft-float -m64 -mno-red-zone -fpic -fno-reorder-blocks
> > -fno-asynchronous-unwind-tables -DNDEBUG -D__ASSEMBLY__ -c
x86_64/entry.S -o
> > x86_64/entry.o
> > x86_64/entry.S: Assembler messages:
> > x86_64/entry.S:317: Error: `1(%eax)'' is not a valid 64 bit
base/index
> > expressionx86_64/entry.S:320: Error: `136+8(%esp)'' is not a
valid 64 bit
> > base/index expression
> 
> that''s odd. could you verify you have the correct line on entry.S
?
> 
> line 317: setnz VCPUINFO_upcall_mask(%rax)
> line 320: movw  UREGS_cs+8(%rsp),%ax
> 
> as well, what compiler version are you using ?
> 
> --
> Vincent Hanquez
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On Wed, 2005-05-18 at 21:53 +0200, Vincent Hanquez
wrote:
> On Wed, May 18, 2005 at 10:59:00AM -0500, David F Barrera wrote:
> > Using the May 17 xen-unstable-src.tgz on x86_64, the following error
> > occurs on a SLES 9 SP1 platform (It builds OK on Fedora Core 4, but it
> > does not boot, and that is another issue):				
> > 
> > gcc -nostdinc -fno-builtin -fno-common -fno-strict-aliasing
-iwithprefix include
> > -Wall -Werror -Wno-pointer-arith -pipe -I/tmp/xen-unstable/xen/include
> > -I/tmp/xen-unstable/xen/include/asm-x86/mach-default -O3
-fomit-frame-pointer
> > -msoft-float -m64 -mno-red-zone -fpic -fno-reorder-blocks
> > -fno-asynchronous-unwind-tables -DNDEBUG -D__ASSEMBLY__ -c
x86_64/entry.S -o
> > x86_64/entry.o
> > x86_64/entry.S: Assembler messages:
> > x86_64/entry.S:317: Error: `1(%eax)'' is not a valid 64 bit
base/index
> > expressionx86_64/entry.S:320: Error: `136+8(%esp)'' is not a
valid 64 bit
> > base/index expression
> 
> that''s odd. could you verify you have the correct line on entry.S
?
They seem different. I am using the May 17 xen-unstable-src.tgz
file.
> 
> line 317: setnz VCPUINFO_upcall_mask(%rax)
I have: 
setnz VCPUINFO_upcall_mask(%eax)# TBF_INTERRUPT -> clear upcall mask
> line 320: movw  UREGS_cs+8(%rsp),%ax
I have:
movw  UREGS_cs+8(%esp),%ax      # Bits  0-15: CS

> 
> as well, what compiler version are you using ?
gcc version 3.3.3 (SuSE Linux): 


-- 
Regards,

David F Barrera
Linux Technology Center
Systems and Technology Group, IBM

"The wisest men follow their own direction. "
                                                        Euripides


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel