Lines Matching refs:system

32 are supplied by the system. Stuff like `__cxa_guard_acquire` and
35 #### linker/ --- /system/bin/linker and /system/bin/linker64
77       # See 'Adding system calls' later.
165 ## Adding libc wrappers for system calls
168 this system call?". The answer is usually "no".
170 The answer is "yes" if the system call is part of the POSIX standard.
172 The answer is probably "yes" if the system call has a wrapper in at
175 The answer may be "yes" if the system call has three/four distinct
182 Adding a system call usually involves:
187   2. Find the right header file to work in by looking up your system call
198      for the first release your system call wrapper will be in. See
206      use the same name as an existing system call (to reduce the amount of
219      what the system call returns from the RETURN VALUE of the man page),
231      the first to add a system call to this version of Android.
238      your system call is exposed in <unistd.h>, for example, your test would go
245      system call is being made.)
253 Some system calls are harder than others. The most common problem is a 64-bit
258 and a foo64(), and whether they will use the same underlying system call or are
259 implemented as two different system calls. It's usually easiest to find a
260 similar system call and copy and paste from that. You'll definitely need to test
267 A general example of adding a system call:
278     xxx; // the new system call you add
297 2. Use of undeclared identifier of the new system call in the test
319 [system/timezone/README.android](https://android.googlesource.com/platform/system/timezone/+/main/R…