New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Polygeist and CIRCT are out of sync #4
Comments
I run into the same issue, and unfortunately think that until Polygeist transforms into more of a publicly maintained project, the best option is to have separate LLVM builds for circt and polygeist. This is also why i updated the README and myself am using two separate builds. |
Thank you for the comment. Just to clarify, "as a fallback use the internal LLVM submodule of Polygeist" in README means to build Polygeist as follows? (assuming the current directory is circt-hls/Polygeist)
|
I think that would work, yes. What i do locally is build polygeist and LLVM separately, and point Polygeist to the LLVM build. I do the same locally as what is done in CI (still working on getting CI to pass - it's very slow and there are some slight issues. But, things are working locally for me!). circt-hls/.github/workflows/build_and_test.yml Lines 107 to 122 in 762c99f
and polygeist building: circt-hls/.github/workflows/build_and_test.yml Lines 131 to 146 in 762c99f
|
Hi,
I frequently update CIRCT. Polygeist is not in sync with CIRCT's MLIR.
I've recently got the following error where
AbstractOperation
no longer exists inPolygeist/llvm-project/mlir/include/mlir/IR/OperationSupport.h
Any suggestions to resolve this conflict?
The text was updated successfully, but these errors were encountered: