Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey @csabahruska,
In preparation for @mpickering and @alt-romes to release an alpha version of
dap
integration w/ GHC, I'd like to ensure that our work with the haskell-estgi-debugger is building along with the comingdap
changes.This PR updates the
external-stg-interpreter
,external-stg
andexternal-stg-syntax
to build with GHC 9.6+.Things done:
Word
andInt
sinceghc-prim
had slightly changed (primop tests pass now ✅ )cabal.project
file was added and it does build with the latestsouffle-haskell-0.4.0.0
and a working version offinal-pretty
-fexternal-ext-stg-gc
and-fexternal-ext-liveness-analysis
-- disabled by default in the cabal file - but enabled by default incabal.project
) to allow users to build thesouffle
generated C++ by hand. This simplifies the build, andrunSouffle
is able to find theext-stg-gc
binary in$PATH
.import Control.Monad
, it was decided thatControl.Monad
should no longer be re-exported frommtl
modules.bzip2
andzlib
.^ these tests should run in CI now
Then in the
haskell-debugger
I'm able to makeext-stg-gc
available onPATH
sorunSouffle
will always be able to find it, when we call theexternal-stg-interpreter
fromhaskell-debugger
.