As far as I can tell, there is a mechanism for dynamically loading the devices into Wrspice at runtime (as devlib). To support this, files in devlib are compiled with -fPIC (position independent code). However, the dynamic loading mechanism is optional and devlib can be statically linked into the wrspice executable. It appears that files are compiled with the -fPIC option in both cases.
This is potentially a performance problem, as under some circumstances gcc can generate considerably slower code. That said, the only way to be sure is to test it and I have not done that.
As far as I can tell, there is a mechanism for dynamically loading the devices into Wrspice at runtime (as devlib). To support this, files in devlib are compiled with -fPIC (position independent code). However, the dynamic loading mechanism is optional and devlib can be statically linked into the wrspice executable. It appears that files are compiled with the -fPIC option in both cases.
This is potentially a performance problem, as under some circumstances gcc can generate considerably slower code. That said, the only way to be sure is to test it and I have not done that.