Displaying 3 results from an estimated 3 matches for "mfp32".
Did you mean:
fp32
2015 Jun 11
2
[LLVMdev] How to pick default floating point ABI?
...; used with a 32-bit ABI
/usr/local/bin/mipsel-unknown-linux-gnu-ld: Warning: a.out uses
-mdouble-float (set by
/opt/toolchain_clang/host/usr/mipsel-unknown-linux-gnu/sysroot/usr/lib/../lib/crt1.o),
/tmp/test-d48db1.o uses -mgp32 -mfp64
How can I change the *fp=64* to *fp=32*? Have tried pass -mfp32 to
mipsel-unknown-linux-gnu-clang++ but with no luck.
Though this is a warning, but it fails to compile Qt.
Yes I known it works if uses *-mips64* etc, but I need mips3.
Please let me know if I'm post to the wrong place, I'm new here.
Thank you.
--
*Regards*
--------------...
2015 Jun 16
2
[LLVMdev] How to pick default floating point ABI?
...be warmly welcomed. In the
> meantime, the best I can suggest is to target mips2 and O32. That
> combination will work and will do the same thing (aside from the
> precise ELF header flags) as mips3 and O32 would.
>
> > How can I change the *fp=64* to *fp=32*? Have tried pass -mfp32 to
> mipsel-unknown-linux-gnu-clang++ but with no luck.
>
> In the current implementation, this is not possible.
>
> This also raises a point I haven't considered yet. The Mips3
> architecture mandates that the FPU implementation is 64-bit, but if
> you're generating...
2015 Jun 16
2
[LLVMdev] How to pick default floating point ABI?
...iler to generate objects
> that can be used on both a 32-bit and 64-bit FPU. In recent compilers
> it is enabled by default. The most likely cause of the warning is some
> inline assembly that doesn't obey the small restrictions that FPXX
> enforces. Assuming, this is the cause –mfp32/-mfp64 should provide a
> work around but I'd recommend updating the inline assembly since this
> will make it easier to port to newer Mips processors.
>
> //
Just tested with xercesc v3, got these warnings (sorry I said error
message in last reply)
> DOMNodeIDMap.s:134: Warn...