Lines Matching full:remark

8 Introduction to the LLVM remark diagnostics
15 There are three main remark types:
58 LLVM: through remark diagnostics, or through serialized remarks.
60 Remark diagnostics
131       The minimum profile count required for an optimization remark to be
176 A typical remark serialized to YAML looks like this:
194 * ``<pass>``: the name of the pass that emitted this remark.
195 * ``<name>``: the name of the remark coming from ``<pass>``.
255 * the absolute file path to the serialized remark diagnostics: a
272 A bitstream remark stream can be identified by the magic number ``"RMRK"`` that
302     The version of the remark entries. This can change independently from the
311     The string table used by the remark entries. The format of the string table
318     The external remark file path that contains the remark blocks associated
326 The block describing a remark entry.
335     The header of the remark. This contains all the mandatory information about
336     a remark.
341     | Remark name   | VBR6 (string table index) |
350     The source location for the corresponding remark. This record is optional.
362     The hotness of the remark. This record is optional.
370     A remark argument with an associated debug location.
386     A remark argument with an associated debug location.
394 The remark container
402     provides a way to serialize the remark entries to a stream while some
413 bitstream remark container type.
429 ``SeparateRemarksFile: the remark entries emitted separately``
447 parsing the remark entries.
452 ``Standalone: the metadata and the remark entries emitted together``
482       <Remark version codeid=2 abbrevid=5 op0=0/>
484     <Remark BlockID=9 NumWords=8 BlockCodeSize=4>
485       <Remark header codeid=5 abbrevid=4 op0=2 op1=0 op2=1 op3=2/>
486       <Remark debug location codeid=6 abbrevid=5 op0=3 op1=99 op2=55/>
487       <Remark hotness codeid=7 abbrevid=6 op0=999999999/>
489     </Remark>
498       <Remark version codeid=2 abbrevid=5 op0=30/>
501     <Remark BlockID=9 NumWords=8 BlockCodeSize=4>
502       <Remark header codeid=5 abbrevid=4 op0=2 op1=1 op2=0 op3=2/>
503       <Remark debug location codeid=6 abbrevid=5 op0=3 op1=99 op2=55/>
504       <Remark hotness codeid=7 abbrevid=6 op0=999999999/>
506     </Remark>
581 Emitting remark diagnostics in the object file
584 A section containing metadata on remark diagnostics will be emitted for the
607     LLVMRemarkEntryRef Remark = NULL;
608     while ((Remark = LLVMRemarkParserGetNext(Parser))) {
609        // use Remark
610        LLVMRemarkEntryDispose(Remark); // Release memory.
615 Remark streamers
621 All remark serialization should go through the main remark streamer, the
623 takes remark objects converted to ``llvm::remarks::Remark``, and takes care of
627 Typically, a specialized remark streamer will hold a reference to the one set
631 that get converted to ``llvm::remarks::Remark`` objects.  Then, clang could set
632 up its own specialized remark streamer that takes ``clang::Diagnostic``
639   their specialized remark streamers that all emit remarks through the same
641 * Re-using the remark infrastructure in ``lib/Remarks``.
642 * Using the same file and format for the remark emitters created throughout the