Fix user programs requiring an explicit exit syscall
#3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kayomn
commented
Nov 16, 2022
| @@ -96,3 +96,11 @@ void* memmove(void *vdst, const void *vsrc, int n) { | |||
| } | |||
| return vdst; | |||
| } | |||
|
|
|||
|
|
|||
| __attribute__((noreturn)) | |||
There was a problem hiding this comment.
As a note, this GCC annotation can be removed should you wish as it's already inferred by calling exit inside the function itself.
kayomn
changed the title
exit syscallexit syscall
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves the issue where user programs need to explicitly call the
exitsystem call before returning frommainor else they will never exit.