Re: Support for Linux on Sparc?

On Tue, 27 May 2003, Thomas Dodd wrote:
>>>At 01:35 PM 4/21/2003 -0400, you wrote:
>>>CP1500 modules # gcc -DMODULE -D__KERNEL__ -O6 -I/usr/src/linux/include
>
>-O6 ?
>could that cause problems? Perhaps try -O2?
...
>>>/usr/src/linux/include/asm/page.h:111: warning: call-clobbered register
>>>used for
>>>  global register variable
...
>
>Is this for 64bit sparc?
>Has anyone trried it on the Opteron yet? It may be a 64bit issue.

As I sent to DB a few days (or weeks) ago... if this is on a sparc/sparc64,
then a simple "gcc -foo" is NOT going to work.  The above register warning
is a neon sign.  Go build a kernel and see what options are being used...

sparc64-linux-gcc -Wp,-MD,kernel/.acct.o.d -D__KERNEL__ -Iinclude -Wall
  -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
  -m64 -pipe -mno-fpu -mcpu=ultrasparc -mcmodel=medlow -ffixed-g4 -fcall-used
  -g5 -fcall-used-g7 -Wno-sign-compare -Wa,--undeclared-regs -pg -nostdinc
  -iwithprefix include -DKBUILD_BASENAME=acct -DKBUILD_MODNAME=acct -c
  -o kernel/.tmp_acct.o kernel/acct.c

Note the -ffixed-g4 and -fcall-used-g7 (among others.)  Basically, to
get anything to work correctly, one needs to do exactly what the kernel
build process will do; and most of that magic is in the arch/.../Makefile.

--Ricky


_______________________________________________
tulip mailing list, [email protected]
To change to digest mode or unsubscribe visit
http://www.scyld.com/mailman/listinfo/tulip