search for: dispflagoptimized

...ne https://github.com/llvm/llvm-project/blob/master/llvm/lib/IR/Verifier.cpp#L1160 there is IR verification which asserts that only in case of `spFlags = DISPFlagDefinition`, the compilation unit (`unit` field) should be present. Otherwise, it should *not* be present. In the crash case, `spFlags = DISPFlagOptimized`. So, I guess, `unit` field should *not* be present, though I do not know the difference between ` DISPFlagDefinition` and ` DISPFlagOptimized`. if that is expected, then we may need to check `nullity` of `DISubprogram::getUnit()` before accessing it at https://github.com/llvm/llvm-project/blob/ma...

...m/llvm/llvm-project/blob/master/llvm/lib/IR/Verifier.cpp#L1160 > there is IR verification which asserts that only in case of `spFlags = > DISPFlagDefinition`, the compilation unit (`unit` field) should be present. > Otherwise, it should *not* be present. In the crash case, `spFlags = > DISPFlagOptimized`. So, I guess, `unit` field should *not* be present, > though I do not know the difference between ` DISPFlagDefinition` and ` > DISPFlagOptimized`. if that is expected, then we may need to check > `nullity` of `DISubprogram::getUnit()` before accessing it at > https://github.com/llvm/...

...routineType(types: !9) !9 = !{null} !10 = !DILocation(line: 2, column: 1, scope: !7) ----------- Now, let's say, in the above IR file, I intentionally make debug info metadata, a kind of invalid, by removing the field 'unit` and by changing the field `spFlags` from `DISPFlagDefinition` to `DISPFlagOptimized` within metadata info !7 as shown below. ----------- ; ModuleID = 'foo.cpp' source_filename = "foo.cpp" target datalayout = "e-m:e-p270:32:32-p271:32:32-p272:64:64-i64:64-f80:128-n8:16:32:64-S128" target triple = "x86_64-unknown-linux-gnu" ; Function Attrs: n...

...m/llvm/llvm-project/blob/master/llvm/lib/IR/Verifier.cpp#L1160 > there is IR verification which asserts that only in case of `spFlags = > DISPFlagDefinition`, the compilation unit (`unit` field) should be present. > Otherwise, it should *not* be present. In the crash case, `spFlags = > DISPFlagOptimized`. So, I guess, `unit` field should *not* be present, > though I do not know the difference between ` DISPFlagDefinition` and ` > DISPFlagOptimized`. if that is expected, then we may need to check > `nullity` of `DISubprogram::getUnit()` before accessing it at > https://github.com/llvm/...