svf-tools 1.0.1228 → 1.0.1230
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "svf-tools",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.1230",
|
|
4
4
|
"description": "* <b>[TypeClone](https://github.com/SVF-tools/SVF/wiki/TypeClone) published in our [ECOOP paper](https://yuleisui.github.io/publications/ecoop20.pdf) is now available in SVF </b> * <b>SVF now uses a single script for its build. Just type [`source ./build.sh`](https://github.com/SVF-tools/SVF/blob/master/build.sh) in your terminal, that's it!</b> * <b>SVF now supports LLVM-10.0.0! </b> * <b>We thank [bsauce](https://github.com/bsauce) for writing a user manual of SVF ([link1](https://www.jianshu.com/p/068a08ec749c) and [link2](https://www.jianshu.com/p/777c30d4240e)) in Chinese </b> * <b>SVF now supports LLVM-9.0.0 (Thank [Byoungyoung Lee](https://github.com/SVF-tools/SVF/issues/142) for his help!). </b> * <b>SVF now supports a set of [field-sensitive pointer analyses](https://yuleisui.github.io/publications/sas2019a.pdf). </b> * <b>[Use SVF as an external lib](https://github.com/SVF-tools/SVF/wiki/Using-SVF-as-a-lib-in-your-own-tool) for your own project (Contributed by [Hongxu Chen](https://github.com/HongxuChen)). </b> * <b>SVF now supports LLVM-7.0.0. </b> * <b>SVF now supports Docker. [Try SVF in Docker](https://github.com/SVF-tools/SVF/wiki/Try-SVF-in-Docker)! </b> * <b>SVF now supports [LLVM-6.0.0](https://github.com/svf-tools/SVF/pull/38) (Contributed by [Jack Anthony](https://github.com/jackanth)). </b> * <b>SVF now supports [LLVM-4.0.0](https://github.com/svf-tools/SVF/pull/23) (Contributed by Jared Carlson. Thank [Jared](https://github.com/jcarlson23) and [Will](https://github.com/dtzWill) for their in-depth [discussions](https://github.com/svf-tools/SVF/pull/18) about updating SVF!) </b> * <b>SVF now supports analysis for C++ programs.</b> <br />",
|
|
5
5
|
"main": "index.js",
|
|
6
6
|
"scripts": {
|
|
@@ -677,8 +677,17 @@ bool SVFIRBuilder::computeGepOffset(const User *V, AccessPath& ap)
|
|
|
677
677
|
else if (const StructType *ST = SVFUtil::dyn_cast<StructType>(gepTy))
|
|
678
678
|
{
|
|
679
679
|
assert(op && "non-const offset accessing a struct");
|
|
680
|
-
//
|
|
681
|
-
|
|
680
|
+
// guard against negative or out-of-bounds struct indices
|
|
681
|
+
// (e.g. rust hashbrown bucket back-offset: gep { ... }, ptr %p, i64 -1)
|
|
682
|
+
// a negative i64 wraps to a huge uint64_t that overflows u32_t,
|
|
683
|
+
// creating an invalid field index that severs points-to tracking
|
|
684
|
+
uint64_t rawIdx = LLVMUtil::getIntegerValue(op).first;
|
|
685
|
+
if (rawIdx >= ST->getNumElements())
|
|
686
|
+
{
|
|
687
|
+
isConst = false;
|
|
688
|
+
continue;
|
|
689
|
+
}
|
|
690
|
+
APOffset idx = (u32_t)rawIdx;
|
|
682
691
|
u32_t offset = pag->getFlattenedElemIdx(llvmModuleSet()->getSVFType(ST), idx);
|
|
683
692
|
ap.setFldIdx(ap.getConstantStructFldIdx() + offset);
|
|
684
693
|
}
|