You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! @djwessel I was reading the snake source code and had a questions regarding the ecall functions inside snake.edl. So in the main.cpp, which is the untrusted app gateway, located at /snake the only ECALL entry point is public void ecall_start_game(); I was wondering if it's necessary to write all other ecall functions like void ecall_speed_up([in, out] struct screen_t* screen, [in, out] struct snake_t* snake);, void ecall_setup_level_on_start([in, out] struct screen_t* screen, [in, out] struct snake_t* snake);, etc inside edl file as we are not really calling them from the untrusted application. They are more sort of like helper functions on the trusted part. Please correct me if I'm wrong. Any response is appreciated!
The text was updated successfully, but these errors were encountered:
Hey @AlexYaoRuihao, to be honest, it has been a long time since I worked on this project, and it was just a part of a course in university. I haven't really worked with SGX since, so I don't think it would be fair for me to give you a potentially wrong answer.
Hello! @djwessel I was reading the snake source code and had a questions regarding the ecall functions inside snake.edl. So in the main.cpp, which is the untrusted app gateway, located at
/snake
the only ECALL entry point ispublic void ecall_start_game();
I was wondering if it's necessary to write all other ecall functions likevoid ecall_speed_up([in, out] struct screen_t* screen, [in, out] struct snake_t* snake);
,void ecall_setup_level_on_start([in, out] struct screen_t* screen, [in, out] struct snake_t* snake);
, etc inside edl file as we are not really calling them from the untrusted application. They are more sort of like helper functions on the trusted part. Please correct me if I'm wrong. Any response is appreciated!The text was updated successfully, but these errors were encountered: