Florian Klaempfl schreef:
Line 17 generates two assembler instructions. Line 22 generates three
assembler instructions. As far as I can see both high(d) and @d[high(d)]
are constants, because d is a global variable.
Is it possible that line 22 will generate 2 assembler instructions in
the futu
Lee, John wrote:
> Does this mean we can't do snapshot on win32? Is there a fix planned? Eg
> couldn't we write a fpc version of cp - guess this would only be a few
> lines or is it more complicated than this?
1) Do you get this error too when building Win32 snapshots?
2) It certainly doesn't mea
> Does this mean we can't do snapshot on win32? Is there a fix planned? Eg
> couldn't we write a fpc version of cp - guess this would only be a few
> lines or is it more complicated than this?
This situation is there already for years.
___
fpc-pascal ma
Vincent Snijders wrote:
> Florian Klaempfl schreef:
>>>
>>>
>>> Line 17 generates two assembler instructions. Line 22 generates three
>>> assembler instructions. As far as I can see both high(d) and @d[high(d)]
>>> are constants, because d is a global variable.
>>>
>>> Is it possible that line 22 w
> > Does this mean we can't do snapshot on win32? Is there a fix planned? Eg
> > couldn't we write a fpc version of cp - guess this would only be a few
> > lines or is it more complicated than this?
> This situation is there already for years.
If I get it right, one is supposed to have CYGWIN for
Technically, this should not happen on ANY version of Windows. But, I
digress. I'll just sit here building my Sparc Linux builds and making
them available for download from my site :)
Robert Wolfe ([EMAIL PROTECTED] / [EMAIL PROTECTED])
Computer Programmer/Analyst & Web Programmer
SRDAR, Roswel
>> > Does this mean we can't do snapshot on win32? Is there a fix planned?
>> Eg
>> > couldn't we write a fpc version of cp - guess this would only be a few
>> > lines or is it more complicated than this?
>> This situation is there already for years.
>
> If I get it right, one is supposed to have C
Wolfe, Robert wrote:
> Greetings all! When building the Sparc Linux port of 2.1.1 from the
> current (as of this email) SVN code, I get the following messages:
Works here.
>
> /home/robert/fpc/compiler/ppc1 -Ur -Ur -Xs -O2 -n -Fi../inc -Fi../sparc
> -Fi../un