Alexander Medvednikov
c64467d92a
* v: distinguish native libc header layouts in cached objects * v: retain native header context for generic cache hits * v: cover cached libc layout reuse after pthread ABI fixes
2.0 KiB
Native inputs in the module cache
With -new-compiler -cc cc, applications importing compress.zstd, including veb
applications, can use the module and program caches. Cached module objects share one
copy of V's bundled zstd implementation in the program translation unit. Other units
use the public declarations embedded in the bundled amalgamation. Changes to the
native source remain cache inputs and invalidate affected entries. Embedded resources in omitted
cached function bodies retain their dependency records after their current content and metadata
are verified. Editing or removing a resource invalidates reuse. Bundled mbedTLS headers are checked
with the selected C preprocessor, using the generated units' C
or Objective-C language, and their active dependencies are tracked. C++ contexts,
custom native configuration directives, SDK macro overrides, renamed SDK bindings, and forced
headers keep the conservative fallback when their original context cannot be reconstructed.
Compiler response files and config/spec files also retain the fallback.
Production, shared, and GNU89 inline modes retain this fallback for bundled mbedTLS headers.
Module object cache keys distinguish system libc headers from V's fallback declarations.
A program import or #include can select system headers for the whole program, changing native
type layouts even in modules whose V source is unchanged. Objects from these two header modes
are kept separate, including when reusing a cache populated by an older compiler.
Set V3_CACHE_TRACE=1 to inspect cache decisions, and use -show-timings to see
monomorphize (cached) on an unchanged build. External native inputs without a safe
ownership or replication policy still fall back to an uncached build. TCC selection
continues to follow the compiler's existing cache eligibility rules.
-print-watched-files and -dump-files parse source bodies to include every embedded resource,
including resources omitted from warm declaration headers.