On 19.03.2012, at 10:14, Adrian Schröter wrote:
Am Sonntag, 18. März 2012, 06:51:56 schrieb Bernhard M. Wiedemann: ..
our gcc46.spec had in the armv5 section - --with-float=softfp
which I changed to =soft for a local build (OBS does not let me branch a broken package). And it made gcc work finally for armv5 - yay! ...
We can do so, that would mean that we don't use hard floating point instructions inside the soft fp ABI anymore.
It sounds sane to me, however, I do not know if we have limited us here on puropose.
Some other compilation errors may come back, because the soft FP support may not be good enough.
Question is how many armv5 with and without fpu unit are out there.
Does it make sense to limit us to the ones with hard fpu ? Or would an armv5 port make no sense at all then ?
IIUC most armv5 CPUs come without FPU, so --with-float=soft is the correct solution. I don't know why we have softfp in there - probably just a screwup :). Either way, the armv5 port is supposed to be the "most compatible common ground" that can run everything the accelerated armv7hf port can not run. So it definitely doesn't make sense to use the FPU. Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org