You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -62,7 +62,7 @@ its [project page](https://itc.rwth-aachen.de/must/).
62
62
63
63
Using TypeART involves two phases:
64
64
65
-
1. Compilation: Compile your code with Clang/LLVM (version 14) using the TypeART LLVM pass plugin. The plugin (1) serializes static type information to a file and (2) instruments relevant allocations. See [Section 1.1](#11-compiling-a-target-code).
65
+
1. Compilation: Compile your code with Clang/LLVM using the TypeART LLVM pass plugin. The plugin (1) serializes static type information to a file and (2) instruments relevant allocations. See [Section 1.1](#11-compiling-a-target-code).
66
66
2. Execution: Run the instrumented program with a TypeART runtime client, which uses the callback data to perform analysis facilitating the static type information. See [Section 1.2](#12-executing-an-instrumented-target-code).
67
67
68
68
### 1.1 Compiling a target code
@@ -279,7 +279,7 @@ To compile and run the demo targets:
279
279
280
280
## 2. Building TypeART
281
281
282
-
TypeART supports LLVM version 14and 18 and CMake version >= 3.20.
282
+
TypeART supports LLVM version 14, 18 and 19, and CMake version >= 3.20.
283
283
284
284
### 2.1 Optional software requirements
285
285
@@ -378,7 +378,7 @@ Example using CMake [FetchContent](https://cmake.org/cmake/help/latest/module/Fe
0 commit comments