perlcc may be experimental, but even if it was pretty reliable, the above would still be a big issue.

AUTOLOAD is often used for dynamic delayed loading of functionality. That speeds up scripts because they do not have to compile functionality they may not use. But it means that even when the script has finished loading, there is no easy way to tell how much more it has to compile.

The best workaround is to have a module you load that doesn't do anything useful, but deliberately makes calls that exercise all of the functionality which would need to be loaded. Then they get autoloaded in time to be compiled by perlcc. This may be somewhat trial and error.

You will have (not can, but will) related problems with functionality loaded on demand with require, and with any module which creates open socket connections (eg to a database) upon loading.