RFC: Remove spec & file analysis

goblint · Dec 1, 2023 · 89698bc · 89698bc
1 parent db49fe9
commit 89698bc
Show file tree

Hide file tree

Showing 66 changed files with 4 additions and 2,306 deletions.
diff --git a/docs/developer-guide/messaging.md b/docs/developer-guide/messaging.md
@@ -47,16 +47,3 @@ The `~loc` argument is optional and defaults to the current location, but allows
 The `_noloc` suffixed functions allow general messages without any location (not even current).
 
 By convention, may-warnings (the usual case) should use warning severity and  must-warnings should use error severity.
-
-### Spec analysis
-
-Warnings inside `.spec` files are converted to warnings.
-They parsed from string warnings: the first space-delimited substring determines the category and the rest determines the text.
-
-For example:
-```
-w1 "behavior.undefined.use_after_free"
-w2 "integer.overflow"
-w3 "unknown my message"
-w4 "integer.overflow some text describing the warning"
-```
diff --git a/scripts/goblint-lib-modules.py b/scripts/goblint-lib-modules.py
@@ -42,8 +42,6 @@
 
     "MessageCategory", # included in Messages
     "PreValueDomain", # included in ValueDomain
-    "SpecCore", # spec stuff
-    "SpecUtil", # spec stuff
 
     "ConfigVersion",
     "ConfigProfile",

diff --git a/scripts/spec/check.sh b/scripts/spec/check.sh
diff --git a/scripts/spec/regression.py b/scripts/spec/regression.py
diff --git a/scripts/spec/regression.sh b/scripts/spec/regression.sh
diff --git a/scripts/spec/spec.sh b/scripts/spec/spec.sh