On 20/01/2011 05:14, Florian Klaempfl wrote:
Am 20.01.2011 04:01, schrieb Michel Catudal:
In the Makefile I see these after I do a fpcmake -Tall. I looked all
over the project and cannot find where I would put the information
so fpcmake would generate a Makefile with : ifeq
($(FULL_TARGET),a
Am 20.01.2011 04:01, schrieb Michel Catudal:
> In the Makefile I see these after I do a fpcmake -Tall. I looked all
> over the project and cannot find where I would put the information
> so fpcmake would generate a Makefile with : ifeq
> ($(FULL_TARGET),avr32-embedded)
>
> Makefile:ifeq ($(FULL_TA
Am 20.01.2011 11:01, schrieb Bernd Mueller:
> Henry Vermaak wrote:
>> On 20/01/11 08:20, Michael Schnell wrote:
>>> On 01/19/2011 05:13 PM, Henry Vermaak wrote:
it's really expensive to trap the illegal instructions and emulate
them.
>>> AFAIK, the trapping is done by the ARM CPU, an
Henry Vermaak wrote:
On 20/01/11 08:20, Michael Schnell wrote:
On 01/19/2011 05:13 PM, Henry Vermaak wrote:
it's really expensive to trap the illegal instructions and emulate them.
AFAIK, the trapping is done by the ARM CPU, anyway, providing the
emulation functions just costs some memory, bu
On 01/20/2011 10:40 AM, Henry Vermaak wrote:
...
This is exactly what I wanted to say, as well. The trap itself is done
by the hardware, the handling of same (if the user land software in fact
does FPU instructions) is very slow and intrusive.
-Michael
_
On Wed, Jan 19, 2011 at 5:18 PM, Henry Vermaak wrote:
> How did it crash? Your crashes may be due to the fact that fpc passes
> floats incorrectly in function calls, too.
I just rechecked, and for FPC-based apps, it simply refuses installing:
W/PackageManager( 89): Native ABI mismatch from pa
On 20/01/11 08:20, Michael Schnell wrote:
On 01/19/2011 05:13 PM, Henry Vermaak wrote:
it's really expensive to trap the illegal instructions and emulate them.
AFAIK, the trapping is done by the ARM CPU, anyway, providing the
emulation functions just costs some memory, but of course it's even
On 01/19/2011 05:13 PM, Henry Vermaak wrote:
it's really expensive to trap the illegal instructions and emulate them.
AFAIK, the trapping is done by the ARM CPU, anyway, providing the
emulation functions just costs some memory, but of course it's even
slower and more intrusive than directly ca
