En/na Luca Olivetti ha escrit:
En/na Florian Klaempfl ha escrit:
grepping for abi_eabi I found that the different syscall convention
is in rtl/linux/arm/syscall.inc, but it is conditioned to
FPC_ABI_EABI, not to FPC_ARMEL, so in order to have a fully eabi
compliant compiler should I use "-dFPC_ARMEL -dFPC_ABI_EABI"?
The changed abi field in the system info record causes FPC_ABI_EABI
being defined. Same for softfloat. -dFPC_ARMEL should be enough and
triggering everything else.
I forced -dFPC_ABI_EABI and the generated ppc1 gives an "qemu: uncaught
target signal 6" (under scratchbox/qemu) or segfaults under real hardware.
nevermind, I found where FPC_ABI is defined in compiler/options.pas.
However, if I omit the "-CfSOFT" while building the compiler I get this:
/home/luca/fpc-svn/rtl/units/arm-linux/system.s: Assembler messages:
/home/luca/fpc-svn/rtl/units/arm-linux/system.s:18046: Error: selected
processor does not support `rfs r0'
/home/luca/fpc-svn/rtl/units/arm-linux/system.s:18049: Error: selected
processor does not support `wfs r0'
/home/luca/fpc-svn/rtl/units/arm-linux/system.s:23962: Error: selected
processor does not support `stfd f0,[r11,#-56]'
/home/luca/fpc-svn/rtl/units/arm-linux/system.s:23963: Error: selected
processor does not support `ldfd f0,[r11,#-56]'
(and much more similar lines)
Bye
--
Luca
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
