Skip to content
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

Tracking issue for linux_syscall #63748

Closed
2 tasks
newpavlov opened this issue Aug 20, 2019 · 3 comments
Closed
2 tasks

Tracking issue for linux_syscall #63748

newpavlov opened this issue Aug 20, 2019 · 3 comments
Labels
B-unstable Blocker: Implemented in the nightly compiler and unstable. C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC O-linux Operating system: Linux T-lang Relevant to the language team, which will review and decide on the PR/issue. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.

Comments

@newpavlov
Copy link
Contributor

newpavlov commented Aug 20, 2019

PR: #63745

Unresolved questions:

  • Should we add syscalls to core or keep only in std?
  • Do we still need the workaround for syscall6 on x86?
@jonas-schievink jonas-schievink added B-unstable Blocker: Implemented in the nightly compiler and unstable. C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. O-linux Operating system: Linux labels Aug 20, 2019
@Centril Centril added the T-lang Relevant to the language team, which will review and decide on the PR/issue. label Aug 20, 2019
@hellow554
Copy link
Contributor

How is a syscall supported in a core environment? I don't think that that will make sense

@newpavlov
Copy link
Contributor Author

In the essence it's not that different from supporting target_arch which we do in core::arch::x86_64, but this time those functions will be feature-gated behind target_os. And since calling syscalls involves just a tiny assembly snippet, it would not cause core bloat. Read the discussion linked in the PR. Also I think this issue is relevant as well: #36193

@joshtriplett
Copy link
Member

@newpavlov I would very much like to use these functions in no_std projects that don't link to std or libc. That would be my primary use case for direct use of syscalls.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
B-unstable Blocker: Implemented in the nightly compiler and unstable. C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC O-linux Operating system: Linux T-lang Relevant to the language team, which will review and decide on the PR/issue. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

5 participants