Support up to LLVM 14

This adds support for LLVM versions up to 14 by: * Bumping the `llvm-pretty` submodule to bring in the changes from GaloisInc/llvm-pretty#109. * Bumping the `llvm-pretty-bc-parser` submodule to bring in the changes from GaloisInc/llvm-pretty-bc-parser#219. * Bumping the `crucible` submodule to bring in the changes from GaloisInc/crucible#1083. * Updating the surrounding documentation accordingly.
GaloisInc · May 26, 2023 · 65e898e · 65e898e
1 parent 48731f1
commit 65e898e
Show file tree

Hide file tree

Showing 6 changed files with 7 additions and 5 deletions.
diff --git a/CHANGES.md b/CHANGES.md
@@ -99,6 +99,8 @@
   see the `mir_*` commands documented in the
   [SAW manual](https://github.com/GaloisInc/saw-script/blob/master/doc/manual/manual.md).
 
+* Support LLVM versions up to 14.
+
 # Version 0.9
 
 ## New Features

diff --git a/README.md b/README.md
@@ -72,7 +72,7 @@ SAW can analyze LLVM programs (usually derived from C, but potentially
 for other languages). The only tool strictly required for this is a
 compiler that can generate LLVM bitcode, such as `clang`. However,
 having the full LLVM tool suite available can be useful. We have tested
-SAW with LLVM and `clang` versions from 3.5 to 12.0, as well as the
+SAW with LLVM and `clang` versions from 3.5 to 14.0, as well as the
 version of `clang` bundled with Apple Xcode. We welcome bug reports on
 any failure to parse bitcode from LLVM versions in that range.
 

diff --git a/deps/crucible b/deps/crucible
diff --git a/deps/llvm-pretty b/deps/llvm-pretty
diff --git a/deps/llvm-pretty-bc-parser b/deps/llvm-pretty-bc-parser
diff --git a/doc/manual/manual.md b/doc/manual/manual.md
@@ -1580,7 +1580,7 @@ The resulting `LLVMModule` can be passed into the various functions
 described below to perform analysis of specific LLVM functions.
 
 The LLVM bitcode parser should generally work with LLVM versions between
-3.5 and 9.0, though it may be incomplete for some versions. Debug
+3.5 and 14.0, though it may be incomplete for some versions. Debug
 metadata has changed somewhat throughout that version range, so is the
 most likely case of incompleteness. We aim to support every version
 after 3.5, however, so report any parsing failures as [on