-
Notifications
You must be signed in to change notification settings - Fork 4
Extract SMIR kompilation into module kmir.kompile
#751
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
Conversation
jberthold
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
| _LOGGER.info(f'Copying file {file}') | ||
| shutil.copy2(LLVM_DEF_DIR / file, target_llvm_path / file) | ||
| return KMIR(target_llvm_path, None, bug_report=bug_report) | ||
| from .kompile import kompile_smir |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This creates an import loop (however only in local scope), that's why I didn't continue with factoring out the compilation code. If that's not a problem I have no objections.
| from pyk.kast.prelude.string import stringToken | ||
|
|
||
| from .build import HASKELL_DEF_DIR, LLVM_DEF_DIR, LLVM_LIB_DIR | ||
| from .kmir import KMIR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here is the loop. In theory we could call KMIR.from_kompiled_kore in this module, which imports the module again.
No description provided.