Reed Kotler c03807a3a5 Fix a problem with dual mips16/mips32 mode. When the underlying processor ...

has hard float, when you compile the mips32 code you have to make sure
that it knows to compile any mips32 routines as hard float. I need to clean
up the way mips16 hard float is specified but I need to first think through
all the details. Mips16 always has a form of soft float, the difference being
whether the underlying hardware has floating point. So it's not really
necessary to pass the -soft-float to llvm since soft-float is always true
for mips16 by virtue of the fact that it will not register floating point
registers. By using this fact, I can simplify the way this is all handled.

llvm-svn: 189690

2013-08-30 19:40:56 +00:00

5.3 KiB

Raw Blame History

View Raw