diff options
| author | Alasdair Armstrong | 2019-10-28 15:11:59 +0000 |
|---|---|---|
| committer | Alasdair Armstrong | 2019-10-28 15:11:59 +0000 |
| commit | 3674c9c1ba813fdaec03666777347f05fe421760 (patch) | |
| tree | 049b7b128892934d5c591a511a4447810d49fe37 /src/interactive.ml | |
| parent | b5bdd10e7ce3eed817d9e0f983cffb41ddd5e46f (diff) | |
Make sure that interactive.ml doesn't transitively depend on lem definitions
Lem definitions from Sail2_values are used in the C and SMT backends
as the definition of what the Sail builtins mean for constant folding
and other operations, but due to Lem renaming issues (we think) if any
part of Sail that RMEM relies on transitively depends on a Lem file
(that is affected by renaming?) it causes issues with inconsistent
assumptions over cmi files.
interactive.ml contains a reference to an AST and an environment which
are used as the implicit state that the interactive toplevel
uses. Commit 8182b700 added an implicit IR reference to the toplevel
which essentially added a dependency on sail2_values.lem by way of
jib.lem. This moves that to a separate file which should solve the
issue.
Diffstat (limited to 'src/interactive.ml')
| -rw-r--r-- | src/interactive.ml | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/src/interactive.ml b/src/interactive.ml index cf5c955b..12a1be64 100644 --- a/src/interactive.ml +++ b/src/interactive.ml @@ -56,8 +56,6 @@ let env = ref Type_check.initial_env let ast = ref (Ast.Defs []) -let ir = ref [] - let arg str = ("<" ^ str ^ ">") |> Util.yellow |> Util.clear |