Re: [fpc-pascal] -O2 internal compiler errors

I’m was not able to replicate this right now outside of the project. There appears to be a vast multitude of errors some of which are fixed by removing “inline” and other which I don’t understand right now. When I have some more free time I’ll try again. Thanks. > On Nov 8, 2017, at 11:13 PM,

[fpc-pascal] installing cross fpc in parallel to systems fpc

Hi, how does fpc and it's makefiles handle the case of installing a cross compiler on a system having fpc installed? The target path will differ and I can set that, but how is the config file .fpc.cfg handled? I'm a bit afraid to mess up the installation not because of fpc but because I'm not

Re: [fpc-pascal] -O2 internal compiler errors

Hi, On Wed, 8 Nov 2017, Ryan Joseph wrote: > When I turn on -O2 I get a never ending stream of internal error > 2009112601 which I think is from various inlined operator overloads > (didn’t do much testing though). Is this a bug or are they not > compatible? Example code to trigger it please,

[fpc-pascal] -O2 internal compiler errors

When I turn on -O2 I get a never ending stream of internal error 2009112601 which I think is from various inlined operator overloads (didn’t do much testing though). Is this a bug or are they not compatible? Regards, Ryan Joseph ___

Re: [fpc-pascal] Memory Leak's in XMLRead unit

On Wed, Nov 8, 2017 at 10:52 AM, African Wild Dog wrote: > 2017-11-07 23:57 GMT-02:00 Michael Van Canneyt : >> >> ... >> > My environment: Linux Debian Stretch 64 bits - Lazarus 1.6.4 - fpc 3.0.2. > > I'm quite impressed with the processing power

Re: [fpc-pascal] Memory Leak's in XMLRead unit

On Wed, 8 Nov 2017, African Wild Dog wrote: 2017-11-07 23:57 GMT-02:00 Michael Van Canneyt : The "memory leak" is the exception object: you are not catching the exception. Change your program to the below, and you'll see that it is not leaking memory in the XML

Re: [fpc-pascal] Memory Leak's in XMLRead unit

2017-11-07 23:57 GMT-02:00 Michael Van Canneyt : > > The "memory leak" is the exception object: you are not catching the > exception. > > Change your program to the below, and you'll see that it is not leaking > memory in the XML routines itself. > > Michael. > In fact,