[PATCH] D33370: Don't verify cross-imported bitcode in FunctionImporter

Mehdi AMINI via Phabricator via llvm-commits llvm-commits at lists.llvm.org
Fri May 19 15:30:45 PDT 2017


mehdi_amini added a comment.

> It turns out that the SrcModule in FunctionImporter is in a really inconsistent intermediate state at the point where I ran the Verifier.

Oh right I forgot about this: lazy-loaded modules, even after materializing metadata, aren't passing the verified. This is super annoying.

> After poking around a bit I came to the conclusion that it probably isn't even desirable to run the full-module verifier on each cross-imported module: Over the course of building the entire project the same module will be verified over and over again, which is a waste of resources. When we want to lazy-load metadata running a whole-module Verifier is also problematic.

There is something I'm missing: I thought the important part of the verifier was to be able to drop stalled debug information which is important for backward compatibility? This is the only reason I suggested doing it at this point of the process (before importing)...


Repository:
  rL LLVM

https://reviews.llvm.org/D33370





More information about the llvm-commits mailing list