Searched refs:MisExpect (Results 1 – 13 of 13) sorted by relevance
18 MisExpect diagnostics are intended to help developers identify and address24 By default MisExpect checking is quite strict, because the use of the32 Because this may be too strict, MisExpect diagnostics are not enabled by40 MisExpect diagnostics are also available in the form of optimization remarks,62 Sampling. MisExpect Diagnostics are compatible with all Profiling formats.
46 MisExpect
16 that the optimizer can make more useful decisions about the code. MisExpect21 The MisExpect checks in the LLVM backend follow a simple procedure: if there is35 We calculate the threshold for emitting MisExpect related diagnostics60 Sampling. MisExpect Diagnostics are compatible with all Profiling formats.
49 MisExpect
147 EnableCFIFixup(false), MisExpect(false), in TargetOptions()365 unsigned MisExpect : 1; variable
64 "MisExpect.cpp",
57 MisExpect.cpp
481 Options.MisExpect = CodeGenOpts.MisExpect; in initTargetOptions()
345 if (CodeGenOpts.MisExpect) { in HandleTranslationUnit()
322 InGroup<MisExpect>;
182 CODEGENOPT(MisExpect , 1, 0) ///< Set when -Wmisexpect is enabled
1274 def MisExpect : DiagGroup<"misexpect">;
4479 Res.getCodeGenOpts().MisExpect = true; in CreateFromArgsImpl()