svf-tools 1.0.1296 → 1.0.1298

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.1296",
3
+ "version": "1.0.1298",
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": {
@@ -201,6 +201,16 @@ public:
201
201
  /// Similar to getPts, this also needs to be implemented in child classes.
202
202
  virtual const NodeSet& getRevPts(NodeID nodeId) = 0;
203
203
 
204
+ /// Convenience bool wrappers: return true if the two operands may/must/partial alias
205
+ inline bool mayAlias(const SVFVar* V1, const SVFVar* V2)
206
+ {
207
+ return alias(V1, V2)!= AliasResult::NoAlias;
208
+ }
209
+ inline bool mayAlias(NodeID node1, NodeID node2)
210
+ {
211
+ return alias(node1, node2)!= AliasResult::NoAlias;
212
+ }
213
+
204
214
  /// Print targets of a function pointer
205
215
  void printIndCSTargets(const CallICFGNode* cs, const FunctionSet& targets);
206
216
 
@@ -221,6 +221,12 @@ public:
221
221
  /// Interface expose to users of our pointer analysis, given two pts
222
222
  virtual AliasResult alias(const PointsTo& pts1, const PointsTo& pts2);
223
223
 
224
+ /// Convenience bool wrappers: return true if the two operands may/must/partial alias
225
+ inline bool mayAlias(const PointsTo& pts1, const PointsTo& pts2)
226
+ {
227
+ return alias(pts1, pts2)!= AliasResult::NoAlias;
228
+ }
229
+
224
230
  /// dump and debug, print out conditional pts
225
231
  //@{
226
232
  void dumpCPts() override