Searched refs:extensions (Results 1 – 8 of 8) sorted by relevance
144 __u64 extensions; member159 __u64 extensions; member175 __u64 extensions; member182 __u64 extensions; member196 __u64 extensions; member220 __u64 extensions; member238 __u64 extensions; member253 __u64 extensions; member261 __u64 extensions; member276 __u64 extensions; member[all …]
90 __u64 extensions; member145 __u64 extensions; member159 __u64 extensions; member221 __u64 extensions; member
460 __u64 extensions; member722 __u64 extensions; member792 __u64 extensions; member798 #define I915_DEFINE_CONTEXT_PARAM_ENGINES(name__,N__) struct { __u64 extensions; struct i915_engine…809 __u64 extensions; member994 __u64 extensions; member
30 __u32 extensions; member
5 clang_format = --commit ${PREUPLOAD_COMMIT} --style file --extensions c,h,cc,cpp
66 extensions implemented in tzcode, and the "least non-standard"70 * GNU extensions `strerrordesc_np` and `strerrorname_np`.81 * `close_range` and `copy_file_range` (Linux-specific GNU extensions).112 * `memfd_create` and `mlock2` (Linux-specific GNU extensions).113 * `renameat2` and `statx` (Linux-specific GNU extensions).205 * GNU extensions `fileno_unlocked`/`strchrnul`
19 FORTIFY is a broad suite of extensions to libc aimed at catching misuses of20 common library functions. Textually, these extensions exist purely in libc, but21 all implementations of FORTIFY rely heavily on C language extensions in order55 at Clang. While GCC also provides a set of language extensions necessary to
91 tests are primarily verifying Android extensions and non-standard behavior