Mulib and and 680x0.library

[shelter]

I noticed with an 030 cpu both the 68030.library and the 680x0.library is loaded.
Any reason for this or can I just remove the 680x0.library?

[indigolemon]

I assume you're running 3.1? In that case 680x0.library is used as a 'stub' by setpatch, and will then load the relevant actual library for your processor (it's used to detect and load the needed lib).

It means if you have the 040 and 060 library in libs: you can swap the disk/image between machines and it will just 'work'.

[shelter]

Oh I forgot. It's OS 3.2.1.

But I guess it's the same behavior there.

[Thomas Richter]

Originally Posted by shelter

I noticed with an 030 cpu both the 68030.library and the 680x0.library is loaded.
Any reason for this or can I just remove the 680x0.library?

The library provides some simple functions to control FPU activity. If I recall correctly, the FPU command line uses it. Other than that, older versions of SetPatch use it as dispatcher to find the proper CPU model. It does not take much space, so you can keep it. Newer versions of SetPatch do not require it anymore, but use it if it is present. In general, it contains the "generic" CPU functions and forwards the calls to the CPU library that is the correct one for your system.