[fpc-devel] FPC ARM7 problems

Jonas Maebe jonas.maebe at elis.ugent.be
Thu Aug 7 15:01:12 CEST 2014

On 07 Aug 2014, at 14:51, Jonas Maebe wrote:

> You can start by compiling individual units with different  
> optimisations to figure out in which unit a bug is triggered. After  
> that, you can put {$optimization off} in that unit after the first,  
> second, third, ... procedure to see in which procedure the problem  
> occurs.

You can of course speed this up by using a binary search: enable  
optimisations for half of the units -> if fail, disable for half of  
those, otherwise enable for half of the other half etc. Similarly,  
within a single unit you can put the {$optimization off} halfway and  
then move it up/down by half every time something fails or doesn't.  
Note that {$optimization off} won't work if you put it in the middle  
of a procedure.


More information about the fpc-devel mailing list