dflemstr
It's a ball.
OK, I know that this has been mentioned and discussed before, but there's never been a general consensus on the subject, nor a centralized source of information. I therefore want to put a few specific questions out there that I hope will be answered quickly, so that this thread can get a quick and painless death.
				
			- Is there a significant performance penalty for using floats on the Pandora (to matter for those of us who don't count the instruction cycles in our code manually)?
 - If so, how big is the impact, specifically? E.g. by how many % can I expect the performance to go down in float-dense code (relative to a processor having a full-fledged pipelined FPU)?
 - Can I use some kind of special compiler, e.g. the CodeSourcery 2007q3 one that supposedly possesses magical powers, or another one, that will delegate float operations to a coprocessor at the flip of an "-f" switch, so that floats perform better?
 - Are explicit (compiler-implemented) softfloats to be preferred?
 - If floats are absolutely out of the question, can anyone recommend a good fixed-point C math library, that has about the same functionality as math.h?
 - There was a thread about this a while ago, but what became of it? What do I as a developer gain by using that library?
 
			
				Last edited by a moderator: 
			
		
	
								
								
									
	
								
							
							
	