Merge pull request #490 from secure-software-engineering/f-FixPointsToSet

Fix points to set

Author: pdschubert

.dockerignore

@@ -1,2 +1,2 @@
 ./docker
-./build
+./build

.github/ISSUE_TEMPLATE/bug_report.md

@@ -46,7 +46,7 @@ Describe here the issue that you are experiencing.
 
 <!-- Which build-* script are you using for the build? -->
 
-**Build Type:** 
+**Build Type:**
   - [ ] cmake
   - [ ] custom build
 

.gitlab-ci.yml

@@ -3,14 +3,14 @@ image: pdschbrt/phasar-build-environment:latest
 stages:
   - build
 
-# install the necessary build tools 
-before_script: 
+# install the necessary build tools
+before_script:
   - git submodule update --init --recursive
-  
+
 build:
   stage: build
   # build all interesting targets
-  script: 
+  script:
     - mkdir -p build
     - cd build
     - echo "checking RAM"

CODING_GUIDELINES.txt

@@ -1,17 +1,17 @@
 Coding Guidelines
 =================
 
-In order to unify the look and feel of the Phasar code base, code should be 
+In order to unify the look and feel of the Phasar code base, code should be
 written according to the LLVM coding guidelines wherever possible. The LLVM
 coding guidelines can be here:
 
 	https://llvm.org/docs/CodingStandards.html
 
-In addition, the pre-commit script in githooks/ has to be copied into the 
+In addition, the pre-commit script in githooks/ has to be copied into the
 ./git/hooks/ directory:
 
 	$ cp githooks/pre-commit .git/hooks/
 
 The script will run some useful clang-tidy checks as well as clang-format over
 the entire code base just before your changes are committed in order to reduce
-the number of unnecessary merge conflicts and to unify the code base. 
+the number of unnecessary merge conflicts and to unify the code base.

CONTRIBUTING.md

@@ -28,7 +28,7 @@ A reviewer may request changes or ask questions during the review. If you are un
 Please remember that you are asking for valuable time from other professional developers.
 
 ## Please Help Us to Improve Phasar
-If you are using PhASAR without the wish or expertise to contribute to its code base, you can still help us by providing valuable feedback using this [web from](https://docs.google.com/forms/d/e/1FAIpQLScUXZcdXZe1rY8VxUKjXhTtrsNX5TysNUO4yD8-gaIHiqqWTQ/viewform). Please also refer to [Contributing to PhASAR](https://github.com/secure-software-engineering/phasar/wiki/Contributing-to-PhASAR). 
+If you are using PhASAR without the wish or expertise to contribute to its code base, you can still help us by providing valuable feedback using this [web from](https://docs.google.com/forms/d/e/1FAIpQLScUXZcdXZe1rY8VxUKjXhTtrsNX5TysNUO4yD8-gaIHiqqWTQ/viewform). Please also refer to [Contributing to PhASAR](https://github.com/secure-software-engineering/phasar/wiki/Contributing-to-PhASAR).
 
 Thanks for contributing to the PhASAR project.
 

LICENSE.txt

@@ -4,22 +4,22 @@ Phasar Release License (MIT license)
 
 Copyright (c) 2017 - 2020 Philipp Schubert and others
 
-Permission is hereby granted, free of charge, to any person obtaining a copy of 
-this software and associated documentation files (the "Software"), to deal in 
-the Software without restriction, including without limitation the rights to 
-use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies 
-of the Software, and to permit persons to whom the Software is furnished to do 
+Permission is hereby granted, free of charge, to any person obtaining a copy of
+this software and associated documentation files (the "Software"), to deal in
+the Software without restriction, including without limitation the rights to
+use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
+of the Software, and to permit persons to whom the Software is furnished to do
 so, subject to the following conditions:
 
-The above copyright notice and this permission notice shall be included in all 
+The above copyright notice and this permission notice shall be included in all
 copies or substantial portions of the Software.
 
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.
 
 
@@ -200,7 +200,7 @@ e main offices of Hwaci. Anyone is free to copy, modify, publish, use, compile,
 eans.
 
 The previous paragraph applies to the deliverable code and documentation in SQL
-ite - those parts of the SQLite library that you actually bundle and ship with 
+ite - those parts of the SQLite library that you actually bundle and ship with
 a larger application. Some scripts used as part of the build process (for examp
 le the "configure" scripts generated by autoconf) might fall under other open-s
 ource licenses. Nothing from these build scripts ever reaches the final deliver
@@ -209,15 +209,15 @@ able SQLite library, however, and so the licenses associated with those scripts
 rary.
 
 All of the deliverable code in SQLite has been written from scratch. No code ha
-s been taken from other projects or from the open internet. Every line of code 
+s been taken from other projects or from the open internet. Every line of code
 can be traced back to its original author, and all of those authors have public
  domain dedications on file. So the SQLite code base is clean and is uncontamin
 ated with licensed code from other projects.
 
 
 JSON
 -------------------------------------------------------------------------------
-MIT License 
+MIT License
 
 Copyright (c) 2013-2019 Niels Lohmann
 

config/DOTGraphConfig.json

@@ -46,4 +46,4 @@
 		"fontsize": "11",
 		"arrowsize": "0.7"
 	}
-}
+}

config/README.txt

@@ -1,13 +1,13 @@
-The files glibc_function_list_v1-04.05.17.conf and 
-llvm_intrinsics_function_list_v1-04.05.17.conf contain a list of all functions 
+The files glibc_function_list_v1-04.05.17.conf and
+llvm_intrinsics_function_list_v1-04.05.17.conf contain a list of all functions
 defined in the GNU libc implementation and LLVM intrinsic functions, respectively.
-The functions are loaded into Phasar on start. When Phasar analyzes LLVM IR 
+The functions are loaded into Phasar on start. When Phasar analyzes LLVM IR
 it frequently observes call-sites that call a function contained in one of those
 lists. Following these calls is usually not desired as a user oftentimes do not
 want to analyze the next level of lowering (to libc). For pseudo functions like
-LLVM intrinsic functions there is no source code to analyze as these functions 
-are only used to describe semantics (an orthogonal approch to adding a new 
-instruction); the code generator is responsible to replace the intrinsic 
-functions with software or hardware implementation for the desired target 
+LLVM intrinsic functions there is no source code to analyze as these functions
+are only used to describe semantics (an orthogonal approch to adding a new
+instruction); the code generator is responsible to replace the intrinsic
+functions with software or hardware implementation for the desired target
 architecture. Phasar models calls to these functions as identity (default) by a
 user can specify a different behavior if desired.

config/TaintConfigSchema.json

@@ -67,4 +67,4 @@ R"(
         }
     }
 }
-)"_json
+)"_json

config/llvm_intrinsics_function_list_v1-04.05.17.conf

@@ -1,30 +1,30 @@
-llvm.va_start 
-llvm.va_end 
-llvm.va_copy 
-llvm.gcroot 
-llvm.gcread 
-llvm.gcwrite 
-llvm.returnaddress 
-llvm.addressofreturnaddress 
-llvm.frameaddress 
+llvm.va_start
+llvm.va_end
+llvm.va_copy
+llvm.gcroot
+llvm.gcread
+llvm.gcwrite
+llvm.returnaddress
+llvm.addressofreturnaddress
+llvm.frameaddress
 llvm.localescape
 llvm.localrecover
 llvm.read_register.i32
 llvm.read_register.i64
 llvm.write_register.i32
 llvm.write_register.i64
-llvm.stacksave 
-llvm.stackrestore 
+llvm.stacksave
+llvm.stackrestore
 llvm.get.dynamic.area.offset.i32
 llvm.get.dynamic.area.offset.i64
-llvm.prefetch 
-llvm.pcmarker 
-llvm.readcyclecounter 
-llvm.clear_cache 
-llvm.instrprof_increment 
-llvm.instrprof_increment_step 
-llvm.instrprof_value_profile 
-llvm.thread.pointer 
+llvm.prefetch
+llvm.pcmarker
+llvm.readcyclecounter
+llvm.clear_cache
+llvm.instrprof_increment
+llvm.instrprof_increment_step
+llvm.instrprof_value_profile
+llvm.thread.pointer
 llvm.memcpy.p0i8.p0i8.i32
 llvm.memcpy.p0i8.p0i8.i64
 llvm.memmove.p0i8.p0i8.i32
@@ -192,7 +192,7 @@ llvm.masked.load.v16f32.p0v16f32
 llvm.masked.load.v2f64.p0v2f64
 llvm.masked.load.v8p0f64.p0v8p0f64
 llvm.masked.load.v8p0f_i32f.p0v8p0f_i32f
-llvm.masked.store.v8i32.p0v8i32 
+llvm.masked.store.v8i32.p0v8i32
 llvm.masked.store.v16f32.p0v16f32
 llvm.masked.store.v8p0f64.p0v8p0f64
 llvm.masked.store.v4p0f_i32f.p0v4p0f_i32f
@@ -240,4 +240,4 @@ llvm.donothing
 llvm.experimental.deoptimize
 llvm.experimental.guard
 llvm.load.relative.iN
-llvm.memcpy.element.atomic.p0i8.p0i8
+llvm.memcpy.element.atomic.p0i8.p0i8