"Maciej W. Rozycki" wrote: > > Well, the number of places a run-time condition exist is small and they > are not performance-critical. > > > I actually don't understand your IDT quote. It requires one to call mfc1 to > > get FCR0. On many CPUs without a FPU, this will generate an exception. Are > > you suggesting that we should catch the exception and from that we conclude > > there is no FPU present? > > I don't have an FPU-less system and I can't check such code. I need to > depend on others (I couldn't test all possible configurations anyway). However, with CONFIG_HAS_FPU approach I know for sure it will work for any MIPS CPU, as long as the programmer specifies it correctly. :-) > If > we have a chance to get an exception we have to catch it, of course > (that's trivial to handle in Linux). > No effort (as in CONFIG_HAS_FPU approach) is still better than trivial or small effort ( as in run-time detection). :-) --- I am very curious what makes you object to the CONFIG_HAS_FPU approach, especially you said earlier it was not about the inability to support both FPU and FPU-less CPUs with the same kernel image. Jun
