https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91512
--- Comment #28 from Richard Biener <rguenth at gcc dot gnu.org> --- Note a possibility would be to emit the packing/unpacking functions as inline functions so whether inlining happens would be decided by the middle-end inlining heuristics. That has the advantage of inlining only at (estimated) hot call sites and honoring limits set for unit and function growth. If the inline function is appropriately declared then the offline copy would continue to reside in libgfortran. Not sure if this enables the same optimization as fully inlining the packing/unpacking in the frontend does.
