AWeb 3.5.09 grinds to a halt- why?

[Minuous]

>AWeb 3.5 (which was included in BB3) halts on my A600 with ACA630 (and also in my clone test environment under WinUAE). If I test it under WinUAE (with same config as my A600) but with adding +FPU... AWeb 3.5 runs just fine without halting issues! I guess it requires an FPU to work (unless there is a way to disable that).

Confirmed. It seems to be compiled with GCC's -m68020-60, which is documented as: "Generate output for a 68060, without using any of the new instructions. This results in code which can run relatively efficiently on either a 68020/68881 or a 68030 or a 68040. The generated code does use the 68881 instructions that are emulated on the 68060." So in other words, that build does require an FPU.
  It would have been better to compile it with -m68020 or (if 68000 compatibility is required) with -m68000.

[Minuous]

>Not necessarily. If no floating point data is used then, most likely, no FPU code will be generated. I don't know how much fp is used but I suspect not much.

Actually there's quite a bit. The internal PNG support as well as the PNG plugin both use the FPU. Also a lot of websites such as http://www.google.com and http://www.yahoo.com crash it if there is no FPU, even with image loading turned off.

I'm working on a backport of AWeb 3.5.10 to SAS/C. If this is successful, I will build it for 68EC020 (and for other CPUs if requested).