t; section to
> > >the link.res script but I don't know if it's supposed to be there
> > or
> > >should it be in another stage, any comments?
> >
> > You need to use {$apptype gui} or use the -WG parameter. For the
> > compiler
> > it is n
...
>>The code generated for the above sample is:
>># [16] c:=a*b;
>>movlU_P$PROJECT1_A,%edx
>>movlU_P$PROJECT1_B,%eax
>>mull%edx
>>movl$0,%edx
>>movl%eax,U_P$PROJECT1_C
>>movl%edx,U_P$PROJECT1_C+4
>>
>>What I want is the above code, but without the "
> Now, concerning "both fpc and delphi". That Delphi code can be
> compiled with FPC is rather good thing but FPC has not to follow
> Delphi. The future of Pascal is not Delphi, it is FreePascal. And,
> no, for once, I am not joking. :-)
Most users expect the same behaviour in delphi and fpc. We g
Peter Vreman a écrit :
Since you ask the question, I suppose you cannot simply
suppress the "movl $0,%edx" line generation [*]. What about
using a compiler directive, something like {$EXTENDEDMUL ON/OFF}
for instance?
I don't like this. This means we have to add directives for all kind of
speci
>>>Since you ask the question, I suppose you cannot simply
>>>suppress the "movl $0,%edx" line generation [*]. What about
>>>using a compiler directive, something like {$EXTENDEDMUL ON/OFF}
>>>for instance?
>>
>> I don't like this. This means we have to add directives for all kind of
>> special cpu
On 29 Jul 2005, at 11:36, Marcel Martin wrote:
But it is a special case because FPC makes it special.
No, it's simply a consequence of the fact that Pascal performs all
calculations using the native integer type by default.
Jonas
___
fpc-pasca
Peter Vreman a écrit :
>Marcel Martin wrote :
Since you ask the question, I suppose you cannot simply
suppress the "movl $0,%edx" line generation [*]. What about
using a compiler directive, something like {$EXTENDEDMUL ON/OFF}
for instance?
I don't like this. This means we have to add directiv
Peter Vreman wrote:
>>Florian Klaempfl a écrit :
>>
>>>Vincent Snijders wrote:
>>>
>>>
>>>
Hi,
Suppose I have the following code:
var
a,b: dword;
c: qword;
begin
a := 1000;
b := 2000;
c := a * b;
writeln(c);
end.
Now
> Florian Klaempfl a écrit :
>> Vincent Snijders wrote:
>>
>>
>>>Hi,
>>>
>>>Suppose I have the following code:
>>>
>>>var
>>> a,b: dword;
>>> c: qword;
>>>
>>>begin
>>> a := 1000;
>>> b := 2000;
>>> c := a * b;
>>> writeln(c);
>>>end.
>>>
>>>Now, although c is large enough to contain
Florian Klaempfl wrote:
Vincent Snijders wrote:
Hi,
Suppose I have the following code:
var
a,b: dword;
c: qword;
begin
a := 1000;
b := 2000;
c := a * b;
writeln(c);
end.
Now, although c is large enough to contain the result only the lower
dword is filled. I can force corre
Florian Klaempfl a écrit :
Vincent Snijders wrote:
Hi,
Suppose I have the following code:
var
a,b: dword;
c: qword;
begin
a := 1000;
b := 2000;
c := a * b;
writeln(c);
end.
Now, although c is large enough to contain the result only the lower
dword is filled. I can force corre
Florian Klaempfl a écrit :
Vincent Snijders wrote:
Hi,
Suppose I have the following code:
var
a,b: dword;
c: qword;
begin
a := 1000;
b := 2000;
c := a * b;
writeln(c);
end.
Now, although c is large enough to contain the result only the lower
dword is filled. I can force corre
Vincent Snijders wrote:
> Hi,
>
> Suppose I have the following code:
>
> var
> a,b: dword;
> c: qword;
>
> begin
> a := 1000;
> b := 2000;
> c := a * b;
> writeln(c);
> end.
>
> Now, although c is large enough to contain the result only the lower
> dword is filled. I can fo
13 matches
Mail list logo