Lines Matching defs:PCH
259 // PCH validator implementation
1378 /// and the PCH file was moved from its original location, try to resolve the
1379 /// file by assuming that header+PCH were moved together and the header is in
1380 /// the same place relative to the PCH.
1386 "No point trying to resolve the file if the PCH dir didn't change");
1611 // Otherwise we have a PCH. It's considered to be "imported" at the first
2340 // PCH.
2397 // Build a list of the PCH imports that got us here (in reverse).
2402 // The top-level PCH is stale.
2441 /// If we are loading a relocatable PCH or module file, and the filename
2576 // MODULE_NAME record. However, PCH files have no MODULE_NAME, and yet still
2754 // Relative paths in a relocatable PCH are relative to our sysroot.
2775 // will already have been validated, but this catches the PCH case.
2779 // Load each of the imported PCH files.
3279 // FIXME: Ignore weak undeclared identifiers from non-original PCH
3932 // In case it was imported by a PCH, there's a chance the user is
4328 // FIXME: We assume that locations from PCH / preamble do not need
4429 // located in the module cache (not for PCH files that could be anywhere
4442 static ASTFileSignature readASTFileSignature(StringRef PCH);
4444 /// Whether \p Stream doesn't start with the AST/PCH file magic number 'CPCH'.
4466 return 0; // PCH
4553 // This is used for compatibility with older PCH formats.
4582 // a PCH file sort of works, but it's a bit wonky.
4994 /// Reads and return the signature record from \p PCH's control block, or
4996 static ASTFileSignature readASTFileSignature(StringRef PCH) {
4997 BitstreamCursor Stream(PCH);
7645 /// Under non-PCH compilation the consumer receives the objc methods
7789 llvm::errs() << "*** PCH/ModuleFile Remappings:\n";
7801 llvm::errs() << "\n*** PCH/Modules Loaded:";
7886 // popping entries that were included/imported from a PCH/module.
7914 // popping entries that were included/imported from a PCH/module.
7951 // lookups). Perform the lookup in PCH files, though, since we don't build
7952 // a complete initial identifier table if we're carrying on from a PCH.
8596 // It's a prefix (preamble, PCH, ...). Look it up by index.
8610 // FIXME: Is this true even if we have an explicit module file and a PCH?
8625 // If there is only a single PCH, return it instead.
8626 // Chained PCH are not supported.
11633 // FIXME: this works around module+PCH performance issue.