Lines Matching refs:BMI

108 It is also called the acronym ``BMI`` genrally.
223 How to produce a BMI
226 It is possible to generate a BMI for an importable module unit by specifying the ``--precompile`` o…
236 The file name of the BMI of a ``primary module interface unit`` should be ``module_name.pcm``.
241 then we can't generate a BMI for the ``importable module unit`` by ``--precompile`` option
288 BMI specified by ``-fmodule-file``, the compiler wouldn't look up again in the directories specified
291 When we compile a ``module implementation unit``, we must pass the BMI of the corresponding
312 Remember that module units still have an object counterpart to the BMI
338 As the diagrams show, we need to compile the BMI from module units to object files and link the obj…
339 (But we can't do this for the BMI from header units. See the later section for the definition of he…
398 When the compiler reads a BMI, the compiler will check the consistency of the corresponding
433 But it is OK to move the BMI as long as the source files remain:
444 …er doesn't want to follow the consistency requirement due to some reasons (e.g., distributing BMI),
445 the user could try to use ``-Xclang -fmodules-embed-all-files`` when producing BMI. For example:
636 Similar to named modules, we could use ``--precompile`` to produce the BMI.
639 Also we could use `-fmodule-header={user,system}` option to produce the BMI for header units
695 Don't compile the BMI
698 Another difference with modules is that we can't compile the BMI from a header unit.
742 In the latter example, the Clang could find the BMI for the ``<iostream>``