You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#137 adapted to changes in the (rather roundabout) way DISubprogram's spFlags field is parsed, which was introduced in LLVM 8.0 (see llvm/llvm-project@adcdc1b). Unfortunately, there is a key mistake in this part of the code:
The llvm-pretty-bc-parser code reverses the order of cases! The LLVM code parses Record[9] if HasSPFlags is true, but in the llvm-pretty-bc-parser code, it's the other way around. This manifests itself by always having the various spFlags fields (e.g., isDefinition) always be set to 0 whenever hasSPFlags is set.
The text was updated successfully, but these errors were encountered:
#137 adapted to changes in the (rather roundabout) way
DISubprogram
'sspFlags
field is parsed, which was introduced in LLVM 8.0 (see llvm/llvm-project@adcdc1b). Unfortunately, there is a key mistake in this part of the code:llvm-pretty-bc-parser/src/Data/LLVM/BitCode/IR/Metadata.hs
Lines 706 to 710 in f4391f7
Compare this to the corresponding LLVM code:
The
llvm-pretty-bc-parser
code reverses the order of cases! The LLVM code parsesRecord[9]
ifHasSPFlags
is true, but in thellvm-pretty-bc-parser
code, it's the other way around. This manifests itself by always having the variousspFlags
fields (e.g.,isDefinition
) always be set to0
wheneverhasSPFlags
is set.The text was updated successfully, but these errors were encountered: