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
{{ message }}
This repository has been archived by the owner on Nov 22, 2022. It is now read-only.
Currently if you make a native eapp (don't link to libc) without an lds/etc the linker will just choose the first function in the file as the entry point (doesn't see a _start).
We need a simple standard way to specify the entry point at compilation time of the eapp. We don't want to have to coordinate with the host app.
The text was updated successfully, but these errors were encountered:
void _start wrapped into an ENCLAVE_START macro or similar is almost certainly the right answer.
Lets us make it slightly smarter later on, and keeps it working for now.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently if you make a native eapp (don't link to libc) without an lds/etc the linker will just choose the first function in the file as the entry point (doesn't see a _start).
We need a simple standard way to specify the entry point at compilation time of the eapp. We don't want to have to coordinate with the host app.
The text was updated successfully, but these errors were encountered: