-
Notifications
You must be signed in to change notification settings - Fork 123
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
[Beacon]Get errors when compile logistic model #184
Comments
Hi, Thanks for bringing this to our notice. The Beacon frontend needs to be updated to accommodate the changes to the backend. For now, you can use the network files already committed here or make changes to the file output by the Beacon frontend so that it's consistent with the committed files. |
Thanks for replying. client (mpc_venv) root@8d3d49437847:/ezpc_dir/EzPC/Beacon# cat ../SCI/networks/inputs/hinet_input4.inp ../SCI/networks/inputs/hinet_labels4.inp | ./../SCI/build/bin/hinet4_beacon r=2 mbits=7 ebits=8
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
Input inp:
Input target:
Value of __tac_var209 : 0
Segmentation fault (core dumped) server (mpc_venv) root@8d3d49437847:/ezpc_dir/EzPC/Beacon# ./../SCI/build/bin/hinet4_beacon r=1 mbits=7 ebits=8 < ./../SCI/networks/inputs/hinet_weights.inp
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
connected
Input layer1W:
Input layer1b:
Input layer2W:
Input layer2b:
Input layer3W:
Input layer3b:
Input layer4W:
Input layer4b:
Value of __tac_var209 : 0
Segmentation fault (core dumped) |
When I follow the instruction in Beacon and want to compile the logistic model with
compile_networks.py
, I find some error happens in compilation time.I check the generated logistic.cpp, and find the headers seem to be wrong(lots of
auto
).PS: the command I use:
The text was updated successfully, but these errors were encountered: