RTSA-lab01-CacheAnalysis/README.md

225 lines
5.6 KiB
Markdown
Raw Normal View History

2022-04-19 10:56:42 +02:00
# RTSA-lab01-CacheAnalysis
In this lab session you will learn how to implement a LRU cache in abstract representation.
2022-04-20 14:03:44 +02:00
The Goal is to implement an LRU must Join in include/AbstractState.h.
The Project can be build, tested and Evaluated with the "helper" script.
2022-04-19 10:56:42 +02:00
2022-04-19 11:13:19 +02:00
## Disclaimer
2022-04-19 10:56:42 +02:00
2022-04-20 14:03:44 +02:00
This is the first time we offer this exercise.
Should you encounter something you think is a Bug, please let me (Nils) know, during lab sessions.
2022-04-19 10:56:42 +02:00
2022-04-20 14:03:44 +02:00
Keep track of the Repository as I may add more features to the script.
Also I do not support the usage of Windows, Linux is free of charge so get a copy.
I am more than happy helping you install Linux on your machine.
2022-04-19 10:56:42 +02:00
## Setup
2022-04-20 14:03:44 +02:00
I recommend using docker and VS Code for setup.
Also check out the recommended extensions in the Docker section.
If you prefer to work from Linux or Mac OS X, check the Dockerfile for dependencies.
Also make sure to have a LLVM13 install.
And export your LLVM13 install to the `$LLVM_DIR` variable, with:
```bash
export LLVM_DIR=path/to/LLVM13
```
2022-04-20 14:03:44 +02:00
2022-04-21 20:40:39 +02:00
### Setup on a Pool PC
You will have to use the poolhelber.sh script instead of the normal helper script.
Get and build llvm from source !!This will take a while!!
```bash
./poolhelper.sh llvm
```
In case you can not finish building llvm in one Sessionn just abort it and later on run this:
```bash
./poolhelper.sh continuellvm
```
Now you have a llvm13 source build.
Remember to use the poolhelper.sh instead of the helper.sh.
2022-04-21 12:50:23 +02:00
### VS Code Setup
1.) Install VS Code on your Distribution or get it from Microsoft.
<https://code.visualstudio.com/>
2.) I recommend you install the following extensions in vs code
clangd,
Clang-Format,
CodeLLDB,
Docker and
Remote Development
For a general C/C++ setup of VS Code (I consider good) see:
<https://ahemery.dev/2020/08/24/c-cpp-vscode/>
Most parts can be skipped, as they are already integrated in this Repo.
2022-04-20 14:03:44 +02:00
### Installing LLVM 13 on Mac OS X
On Darwin you can install LLVM 13 with [Homebrew](https://brew.sh/):
```bash
brew install llvm@13
```
If you already have an older version of LLVM installed, you can upgrade it to
LLVM 13 like this:
```bash
brew upgrade llvm
```
Once the installation (or upgrade) is complete, all the required header files,
libraries and tools will be located in `/usr/local/opt/llvm/`.
### Installing LLVM 13 on Ubuntu
On Ubuntu Bionic, you can [install modern
LLVM](https://blog.kowalczyk.info/article/k/how-to-install-latest-clang-6.0-on-ubuntu-16.04-xenial-wsl.html)
from the official [repository](http://apt.llvm.org/):
```bash
wget -O - https://apt.llvm.org/llvm-snapshot.gpg.key | sudo apt-key add -
sudo apt-add-repository "deb http://apt.llvm.org/bionic/ llvm-toolchain-bionic-13 main"
sudo apt-get update
sudo apt-get install -y llvm-13 llvm-13-dev llvm-13-tools clang-13
```
This will install all the required header files, libraries and tools in
`/usr/lib/llvm-13/`.
2022-04-19 10:56:42 +02:00
2022-04-20 14:03:44 +02:00
### Building LLVM 13 From Sources
2022-04-19 10:56:42 +02:00
2022-04-20 14:03:44 +02:00
Building from sources can be slow and tricky to debug. It is not necessary, but
might be your preferred way of obtaining LLVM 13. The following steps will work
on Linux and Mac OS X:
```bash
git clone https://github.com/llvm/llvm-project.git
cd llvm-project
git checkout release/13.x
mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=Release -DLLVM_TARGETS_TO_BUILD=host -DLLVM_ENABLE_PROJECTS=clang <llvm-project/root/dir>/llvm/
cmake --build .
```
For more details read the [official
documentation](https://llvm.org/docs/CMake.html).
This will install all the required header files, libraries and tools in `your/llvm/build/path`.
2022-04-20 14:03:44 +02:00
### Setting up Docker
2022-04-19 10:56:42 +02:00
1.) install docker and VS Code on your Distribution.
2022-04-20 09:55:54 +02:00
<https://docs.docker.com/get-docker/>
2022-04-19 10:56:42 +02:00
2022-04-20 09:55:54 +02:00
<https://code.visualstudio.com/>
2022-04-19 10:56:42 +02:00
For this setup you cannot use the OSS version of VS code or the version from Snap, as the remote development extensions will not work.
2022-04-20 14:03:44 +02:00
2.) I recommend you install the following extensions in vs code
2022-04-19 10:56:42 +02:00
2022-04-20 09:55:54 +02:00
clangd,
2022-04-20 10:15:56 +02:00
Clang-Format,
2022-04-20 09:55:54 +02:00
CodeLLDB,
Docker and
2022-04-19 10:56:42 +02:00
Remote Development
2022-04-20 10:15:56 +02:00
For a general C/C++ setup of VS Code (I consider good) see:
<https://ahemery.dev/2020/08/24/c-cpp-vscode/>
Most of the setup can be skipped
2022-04-19 10:56:42 +02:00
3.) Use the helper script to build and run a Container
2022-04-20 14:03:44 +02:00
```bash
./helper.sh docker
```
2022-04-19 10:56:42 +02:00
This will build a docker image and run a Docker container with the current directory mounted.
2022-04-20 10:15:56 +02:00
The Docker container can later be started from the Docker VS Code extension.
2022-04-19 10:56:42 +02:00
4.) Attach VS Code to the container, in the Docker Tab, and start developing
## Debugging
2022-04-20 14:03:44 +02:00
When you are using VS Code you can simply use the Debugging Tab, I prepared a debug script for you.
2022-04-19 11:13:19 +02:00
You can also set the following variables in the CacheAnalysisPass/CacheAnalysisPass.cpp file, for more output:
```cpp
// Development Options
bool PrintAddresses = false;
bool PrintEdges = false;
bool PrintEdgesPost = false;
bool DumpToDot = false;
bool DumpNodes = false;
```
2022-04-19 10:56:42 +02:00
## Use the Helper script
2022-04-20 09:55:54 +02:00
### Initial Setup
2022-04-19 10:56:42 +02:00
2022-04-20 14:03:44 +02:00
```bash
./helper.sh all
```
2022-04-19 10:56:42 +02:00
To get a list of what the helper script can do simply type
2022-04-20 14:03:44 +02:00
```bash
./helper.sh
```
2022-04-20 09:55:54 +02:00
### Run
2022-04-19 10:56:42 +02:00
Run the pass on a single test.
fft1 is recommended during development.
2022-04-20 14:03:44 +02:00
```bash
./helper.sh run fft1
```
2022-04-20 09:55:54 +02:00
### Eval
2022-04-19 10:56:42 +02:00
2022-04-20 09:55:54 +02:00
Runs the Pass on a set of tests and also prints the expected results.
2022-04-19 10:56:42 +02:00
This will be used to measure correctness of you implementation.
2022-04-20 14:03:44 +02:00
```bash
./helper.sh eval
```
2022-04-19 10:56:42 +02:00
## Use the Terminal (Obsolete if script is used)
This section is not needed, fi you are using the script but for the sake of completeness it is provided anyways.
Initial Setup:
2022-04-20 14:03:44 +02:00
```bash
mkdir build
cd build
cmake -DLT_LLVM_INSTALL_DIR=$LLVM_DIR ../CacheAnalysisPass/
make
cd ..
```
2022-04-19 10:56:42 +02:00
Run:
2022-04-20 14:03:44 +02:00
```bash
opt -load-pass-plugin build/libCacheAnalysisPass.so \
-passes=lru-misses test/crc.ll
```