From b9e9e0cdb15216c09137518615757b3737155a55 Mon Sep 17 00:00:00 2001 From: Will Dietz Date: Thu, 4 May 2017 01:49:46 -0500 Subject: [PATCH] MemModel: quickfix hack for changes in gep_type_iterator behavior. See ongoing discussion for context: https://github.com/unsw-corg/SVF/pull/18 Mostly I'm just curious what this does to results on our programs, this is likely not the right thing to do. --- lib/MemoryModel/MemModel.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/MemoryModel/MemModel.cpp b/lib/MemoryModel/MemModel.cpp index 9bd65f987..01c0d172d 100644 --- a/lib/MemoryModel/MemModel.cpp +++ b/lib/MemoryModel/MemModel.cpp @@ -193,7 +193,7 @@ bool SymbolTableInfo::computeGepOffset(const llvm::User *V, LocationSet& ls) { // Handling array types, skipe array handling here // We treat whole array as one, then we can distinguish different field of an array of struct // e.g. s[1].f1 is differet from s[0].f2 - if(isa(gi.getIndexedType())) + if(gi.isBoundedSequential()) continue;