Marco van de Voort wrote:
>>fpcmake -Tall
>>make distclean
>>make all install OPT=-vt CPU_TARGET=arm OS_TARGET=linux
>>CROSSBINDIR=d:\fpc\binutils\win32-arm-elf BINUTILSPREFIX=arm-elf-
>>INSTALL_PREFIX=d:\FPC\2.0.0 >d:\FPC\build-win32-arm-linux.log
>>and then all seems to run ok.
>>
>>-but no ppc
> fpcmake -Tall
> make distclean
> make all install OPT=-vt CPU_TARGET=arm OS_TARGET=linux
> CROSSBINDIR=d:\fpc\binutils\win32-arm-elf BINUTILSPREFIX=arm-elf-
> INSTALL_PREFIX=d:\FPC\2.0.0 >d:\FPC\build-win32-arm-linux.log
> and then all seems to run ok.
>
> -but no ppccrossarm.exe was created in
Hi there,
not very familiar with gnu binutils stuffs and i tried in a first step
to build correctly arm-linux cross compiler.
according to buidFaq, it was just necessary to run :
fpcmake -Tall
make distclean
make all install OPT=-vt CPU_TARGET=arm OS_TARGET=linux
CROSSBINDIR=d:\fpc\binutils\win3
> I would suggest an "experimental" solution {$inline unsafe ?} which does the
> inline without checks, and maybe gives a warning at compiletime: Warning:
> inlined func/proc might be unsafe.
The used registers still have to be known. For pascal code this is info that
is gained during the compila
I would suggest an "experimental" solution {$inline unsafe ?} which does the
inline without checks, and maybe gives a warning at compiletime: Warning:
inlined func/proc might be unsafe.
Could save some code and some exection time.
I do not understand the argument with e.g. EBP usage. I would say
On Tue, Aug 02, 2005 at 01:46:11PM +0200, Marco van de Voort wrote:
> > >> Sorry, Where I can found them?
> > >
> > >
> > > I don't know; normally you must compile them yourself, but I suppose
> > > they can be downloaded from various sites.
> >
> > Including the fpc ftp server:
> > ftp://ftp.fr
