We have discovered that various places in the JDK 1.1.x
AWT code make excessive use of double precision floating point math routines.
On a CPU without floating point support (or slow FPU) this can lead to
excessive startup times as AWT initializes. On a 486 we see a couple of
minutes delay, on a PPC860 we see something like a 20 minute delay which of
course is totally unacceptable (as is anything over a few seconds or more).

The particular code that is causing the problems is in img_colors.c where
init_matrices() and init_virt_cmap() hammer on floating point and library
routines.