From: Bryan R. <br...@ix...> - 2001-02-21 06:54:13
|
"M. R. Brown" wrote: > Hmm, my assumption (I could be wrong) was that SH4_BIT|SH3E_BIT weren't in > the the -m4-nofpu flag because all FP code generation is supposed to be > disabled. The question I had asked before was, why is this flag necessary > in the kernel (e.g. what does it matter if FP code generation is active or > not), but I hadn't gotten a response (I thought it was explained before > though). I guess what I'm saying is I think leaving those *_BITs off is > an internal gcc hack, so that it does sh4 insn scheduling, etc. but > doesn't do hardware floating-point, so that should probably stay off > (unless it's breaking something for you). Hmmm... Well, even with the patches I posted previously, I'm having trouble building the Linux kernel (2.4.1 out of LinuxSH CVS)... the problem is with our old friends __sdivsi3_i4, __udivsi3_i4, __udivsi3 and __sdivsi3. They are preventing linkage because they're undefined. Any idea how to fix this problem? I'm going to try not setting that SH4 bit, and hope that fixes it... Regards, Bryan -- Bryan Rittmeyer mailto:br...@ix... Ixia Communications 26601 W. Agoura Rd. Calabasas, CA 91302 |