Update for LLVM 6.0.0 #38
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Relevant LLVM changes for updating to v6.0.0 from v4.0.0:
IsPostDominatorsmember ofllvm::DominanceFrontierBasehas become a template parameter (https://reviews.llvm.org/D35315).llvm::Function::getArgumentListhas been dropped in favour ofllvm::Function::arg_begin,llvm::Function::arg_endandllvm::Function::args(https://reviews.llvm.org/rL298010).tool_output_filehas been renamedToolOutputFile.FindAllocaDbgDeclarehas been replaced withFindDbgAddrUses, which returns a list of zero or onellvm.dbg.declareintrinsics plus zero or morellvm.dbg.addrintrinsics (upcast asDbgInfoIntrinsicobjects) (https://reviews.llvm.org/D37768).I've run the test script for the
mem_leakdirectory and it all looks fine – could you advise any further testing that needs to be done?Many thanks!
Jack