Subject: Re: speedy FP
To: None <port-arm32@NetBSD.ORG>
From: Chris Rutter <chris@collegium.co.uk>
List: port-arm32
Date: 04/10/1997 18:22:27
In message <9704101704.AA01286@sun52.cambridge> you recently said:

> Except of course, that you will have to ensure that the compiler hasn't used 
> the link register (r14) in any way, and that it is safely stored on the stack 
> for the return instruction.  So you will need specially compiled code to 
> handle this.

 You could always add a "NOP before FP" option in gcc, which would always
place a MOV R0,R0 before any FP instruction, which could be used to fill
in space. Of course, this is a complete kludge, but it would work.

 Better would of course to get a GCC (or even Norcroft CC) that does FP
inlining -- of course, this isn't always so necessary, as most *really*
intensive FP code is written natively in ARM code anyway.

Chris.
-- 
 // Chris Rutter <chris@fluff.org>
 /  QTMPlay v2.26b (http://www.fluff.org/widget/)