-
Notifications
You must be signed in to change notification settings - Fork 129
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
Failed to compile concrete-ml models on Ubuntu #485
Comments
Hello @weimingma , sorry to hear your troubles using Concrete ML.
Do you mean a VM or docker container? Also are on an ARM system or x86? |
Hi @fd0r , Appreciate for your prompt reply. It's a VM and x86. Let me know if need more info. Thanks. |
Hello again @weimingma , I discussed with my colleagues but we can't find an obvious explanation from the information we have now. Could you please check your We never tested Concrete in a VM afaik so that would allow us to replicate your issue and in the future add a test for it in our CI. |
@fd0r The ldd version is: ldd (Ubuntu GLIBC 2.31-0ubuntu9.14) 2.31. I am trying to get HW related info and fulltrace and will get back to you later. Thanks! |
Alright so that's probably not an issue with |
Hi @fd0r I have tried several times in the case. Unfortunately, there is no Python traceback shown. There is only llvm logs shown after the model is compiled in my initial post. Also, the following shown at the end of the logs:
Please let me know if you were requesting any other logs. |
@weimingma an Illegal instruction could mean your CPU isn't exposing aes cpu instructions to the VM. Could you run |
@youben11 Followed your comments, I have confirmed that the compiling failure was due to lack of aes flag on the VM cpu. This issue is resolved after adding aes to my VM. I am closing this issue. Really apprecite your help~ |
Summary
Cannot compile concrete-ml AI models for example code
Description
or
On either environment above, step by step procedure someone should follow to trigger the bug:
minimal POC to trigger the bug
The text was updated successfully, but these errors were encountered: