Re: [fpc-devel] Inline assembler.

2012-07-20 Thread Konstantin
but this is probably not the way you want to go ;-). Konstantin ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel

Re: [fpc-devel] Cross compiling x86 on amd64, linking to crtbegin.o etc.

2012-07-16 Thread Konstantin
Sven Barth schrieb: Am 11.07.2012 16:36, schrieb Konstantin: Hello! Free Pascal has been designed to run on several platforms on many architectures which is a neat feature. The executable name is chosen accordingly - ppc386, ppcx64 etc. to be able to have many at the same time on the same

[fpc-devel] Cross compiling x86 on amd64, linking to crtbegin.o etc.

2012-07-11 Thread Konstantin
d comments to the Gentoo bug report above. Have fun, Konstantin ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel

Re: [fpc-devel] Bug: compilation loop in 2.0.2 when using -So

2006-08-18 Thread Konstantin Münning
Tomas Hajny wrote: Jonas Maebe wrote: On 17 aug 2006, at 21:40, Konstantin MĂźnning wrote: There are some other inconsistencies to previous versions of FPC and Borland Pascal like assembler syntax and pointer addition (inc(Pointer,LongInt) does not work anymore). Please (as always) post

Re: [fpc-devel] Bug: compilation loop in 2.0.2 when using -So

2006-08-18 Thread Konstantin Münning
Jonas Maebe wrote: On 17 aug 2006, at 21:40, Konstantin Münning wrote: There are some other inconsistencies to previous versions of FPC and Borland Pascal like assembler syntax and pointer addition (inc(Pointer,LongInt) does not work anymore). Please (as always) post a test program

Assembler (Intel) inconsistencies in 2.0.x, Was: Re: [fpc-devel] Bug: compilation loop in 2.0.2 when using -So

2006-08-18 Thread Konstantin Münning
Jonas Maebe wrote: On 17 aug 2006, at 21:40, Konstantin Münning wrote: There are some other inconsistencies to previous versions of FPC and Borland Pascal like assembler syntax and pointer addition (inc(Pointer,LongInt) does not work anymore). Please (as always) post a test program

Re: Assembler (Intel) inconsistencies in 2.0.x, Was: Re: [fpc-devel] Bug: compilation loop in 2.0.2 when using -So

2006-08-18 Thread Konstantin Münning
Jonas Maebe wrote: On 18 aug 2006, at 13:36, Konstantin Münning wrote: PROGRAM Original; {$ASMMODE Intel} PROCEDURE Test(p:Pointer;l:LongInt;w:Word;b:Byte);ASSEMBLER; ASM mov eax,[p] mov eax,[l] mov ax,[w] mov al,[b] END; BEGIN END. This program is like the code

Re: [fpc-devel] removed MaxAvail,MemAvail,HeapSize

2005-05-23 Thread Konstantin Münning
Florian Klaempfl wrote: Konstantin Münning wrote: By the way, I've found the following code in compiler/cclasses.pas when I searched for the whereabouts of maxavail/memavail and there were some more like this in the sources: {$ifdef HASGETHEAPSTATUS} status:=GetFPCHeapStatus

Re: [fpc-devel] removed MaxAvail,MemAvail,HeapSize

2005-05-23 Thread Konstantin Münning
Hi Micha! Thanks for the amusing comments :-). Let me add some of mine. Micha Nelissen wrote: On Mon, 23 May 2005 02:29:48 +0200 Konstantin Münning [EMAIL PROTECTED] wrote: But when there is no memory left and you need some you can't behave perfect. Please let it be the programmers choice

Re: [fpc-devel] removed MaxAvail,MemAvail,HeapSize

2005-05-23 Thread Konstantin Münning
Jonas Maebe wrote: On 23 mei 2005, at 02:29, Konstantin Münning wrote: What would you suggest to return under an OS like Windows, Mac OS X or Linux? The current free memory of the OS? Free memory + buffer cache - minimal buffer cache size enforced by the OS? The previous + available swap

[fpc-devel] removed MaxAvail,MemAvail,HeapSize

2005-05-22 Thread Konstantin Münning
day, -- Konstantin Münning ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel

Re: [fpc-devel] removed MaxAvail,MemAvail,HeapSize

2005-05-22 Thread Konstantin Münning
Florian Klaempfl wrote: Konstantin Münning wrote: Hi everybody! Why in fact were MaxAvail,MemAvail,HeapSize removed from the RTL? The explanation in install/doc/whatsnew.txt is puzzling me a bit: - Removed MaxAvail, MemAvail, HeapSize due to their unreliability (bogus/misleading

Re: [fpc-devel] removed MaxAvail,MemAvail,HeapSize

2005-05-22 Thread Konstantin Münning
Jonas Maebe wrote: On 23 May 2005, at 00:56, Konstantin Münning wrote: No. Either you catch exceptions resulting from a lack of memory and recover, and then you have the same checking as before, except that the check happens atomically (by the OS: you ask for more memory

Re: [fpc-devel] bug 3626

2005-02-02 Thread Konstantin Münning
as it may be an unintentional error but if the compiler compiles int64 integer as int64temp := integer; int64 int64temp it would be just the intended behaviuor in any 'normal' situation I can imagine. Have a nice day, -- Konstantin Münning