<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'><div dir='ltr'>
> No, when building with Android NDK using the armeabi-v7a ABI, hard floats are<br><div>> used. This works on ARMv7, which means a lot of devices, and certainly the<br>> majority.<br><br>But then every other system gets the rough 1000 factor performance hit that started<br>this thread since all other CPU have to do a system call to execute the float operation.<br>Designing for a single handset family is not that scalable.<br><br>> > The ARM<br>> > softfloat overhead is not that great and the coding required to get<br>> > access to the GPUs is suitable that developers will implement them<br>> > for optimisations.<br>> <br>> Soft floats are insanely slow on Android in my experience.<br><br>A factor of 10 or 20 over hard floats? Sound about right? The factor 1000 is for code<br>that uses FPU instructions on systems without the FPU support. That I would call<br>insanely slow but you can choose which way you go here.<br><br>> You got an FPU on most devices, you can compile for hard floats, activate ARM<br>> NEON if you wish too, and even check for cpu features at runtime. I don't see<br>> why you want to use the GPU for optimization.<br><br>Man, the recent chipsets have 6 of these pipelines - designed for graphics processing<br>but sitting there waiting for audio DSP.<br><br>Regards, nick.<br></div> </div></body>
</html>