Home
last modified time | relevance | path

Searched refs:extensions (Results 1 – 8 of 8) sorted by relevance

/bionic/libc/kernel/uapi/drm/
Dxe_drm.h144 __u64 extensions; member
159 __u64 extensions; member
175 __u64 extensions; member
182 __u64 extensions; member
196 __u64 extensions; member
220 __u64 extensions; member
238 __u64 extensions; member
253 __u64 extensions; member
261 __u64 extensions; member
276 __u64 extensions; member
[all …]
Dv3d_drm.h90 __u64 extensions; member
145 __u64 extensions; member
159 __u64 extensions; member
221 __u64 extensions; member
Di915_drm.h460 __u64 extensions; member
722 __u64 extensions; member
792 __u64 extensions; member
798 #define I915_DEFINE_CONTEXT_PARAM_ENGINES(name__,N__) struct { __u64 extensions; struct i915_engine…
809 __u64 extensions; member
994 __u64 extensions; member
Dexynos_drm.h30 __u32 extensions; member
/bionic/
DPREUPLOAD.cfg5 clang_format = --commit ${PREUPLOAD_COMMIT} --style file --extensions c,h,cc,cpp
/bionic/docs/
Dstatus.md66 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`
Dclang_fortify_anatomy.md19 FORTIFY is a broad suite of extensions to libc aimed at catching misuses of
20 common library functions. Textually, these extensions exist purely in libc, but
21 all implementations of FORTIFY rely heavily on C language extensions in order
55 at Clang. While GCC also provides a set of language extensions necessary to
Dnative_allocator.md91 tests are primarily verifying Android extensions and non-standard behavior