-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Add getentropy(2)'s syscall number as a const #108
Merged
Merged
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
I'm not convinced that the NR_* naming scheme is ideal, but it's pretty good. I didn't recognize any other syscall numbers in the file, so I started a new section.
The build failures are on Windows and seem unrelated. |
cc @semarie |
alexcrichton
added a commit
that referenced
this pull request
Dec 18, 2015
Add getentropy(2)'s syscall number as a const
Thanks! |
Susurrus
pushed a commit
to Susurrus/libc
that referenced
this pull request
Mar 26, 2017
… functions This commit provides a new implementation for ioctl that is much more generic, allowing for clients to use send any manner of ioctl requests at special files. The implementation provides two main features that help to raise the level of abstraction over that provided by libc. 1. The module now provides functions that provide the same functionality as the linux kernel _IO* macros. These are used frequently in the linux kernel for building ops for ioctls. The use of these helper functions are not required. 2. Functions are provided for the 3 main types of ioctl usage patterns (read, write, and execute). For many subystems, the read() call which returns a Result<T> and the write calls taking a &T provide a nice interface. All of the methods wrapping ioctl are unsafe and will probably need to remain that way unless knowledge of the semantics of every possible ioctl call are added to the nix library. The best that exists for ioctls are some conventions around the op, but even these conventions are really only used for newer devices added to the kernel. This change resolves rust-lang#108
danielverkamp
pushed a commit
to danielverkamp/libc
that referenced
this pull request
Apr 28, 2020
Need to bring codegen units back to only one for now
danielverkamp
pushed a commit
to danielverkamp/libc
that referenced
this pull request
Apr 28, 2020
* avx: _mm256_loadu_pd * avx: _mm256_storeu_pd * avx: _mm256_loadu_ps * avx: _mm256_storeu_ps * avx: fix _mm256_storeu_pd and _mm256_storeu_ps * avx: _mm256_loadu_si256 * avx: _mm256_undefined_si256 * avx: _mm256_maskload_pd * avx: _mm256_maskstore_pd * Attempt to fix CI (rust-lang#108) Need to bring codegen units back to only one for now * [x86] sse4.2 add docs for _SIDD_EQUAL_RANGES (rust-lang#107) - Add docs for the _SIDD_EQUAL_RANGES mode * Add _MM_TRANSPOSE4_PS pseudo-macro. (rust-lang#106) This adds a strange macro, which I've replaced with a function, because it seems there are not many better alternatives. Also adds a test, and `#[allow(non_snake_case)]` to `#[simd_test]`. * Fix i586 tests * Implement bitwise SSE ops & _mm_cmp*_ss (rust-lang#103) * Add _mm_{and,andnot,or,xor}_ps * Add _mm_cmpeq_ss * Add _mm_cmplt_ss * Add _mm_cmple_ss * Add _mm_cmpgt_ss * Add _mm_cmpge_ss * Add _mm_cmpneq_ss * Add _mm_cmpnlt_ss * Add _mm_cmpnle_ss * Add _mm_cmpngt_ss * Add _mm_cmpnge_ss * Add _mm_cmpord_ss * Add _mm_cmpunord_ss * Fix _mm_{and,andnot,or,xor}_ps tests for i586 LLVM for i586 doesn't seem to generate `andps`, and instead generates 4 `and`s. Similar for the other operations. * avx: _mm_maskload_pd * avx: _mm_maskstore_pd * avx: _mm256_maskload_ps * avx: _mm256_maskstore_ps * avx: _mm_maskload_ps, _mm_maskstore_ps * avx: _mm256_movehdup_ps * avx: _mm256_moveldup_ps
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.
I'm not convinced that the NR_* naming scheme is ideal, but it's pretty
good.
I didn't recognize any other syscall numbers in the file, so I started a
new section.