Searched refs:no (Results 1 – 11 of 11) sorted by relevance
| /bionic/libc/include/sys/ |
| D | cdefs.h | 197 #define __packed error: no __packed for this compiler
198 #define __aligned(x) error: no __aligned for this compiler
199 #define __section(x) error: no __section for this compiler
263 #define __RENAME(x) no renaming in kernel or standalone environment
|
| /bionic/ |
| D | ABI-bugs.txt | 6 off_t is 32-bit. There is off64_t, but no _FILE_OFFSET_BITS support.
|
| /bionic/libc/arch-mips/string/ |
| D | memset.S | 186 beq a2,t8,.Lchk8w # when a2==t8, no 64-byte chunks
196 # For "a2" below 160 there will be no such "pref 30 safe" 64-byte chunk.
|
| D | memcpy.S | 107 beq a2,t8,.Lchk8w # if a2==t8, no 64-byte chunks
355 beq a2,t8,.Lua_chk1w # when a2=t8, no 32-byte chunk
|
| /bionic/libc/ |
| D | CAVEATS | 8 slower code for no good reason (even when so-called zero-cost exception schemes are
|
| D | SYSCALLS.TXT | 16 # - each parameter type is assumed to be stored on 32 bits, there is no plan to support
29 # and no stub should be generated for those architectures marked with -1.
|
| D | NOTICE | 2362 This software is provided ``as is'', and comes with no warranties
2363 of any kind. I shall in no event be liable for anything that happens
|
| /bionic/libstdc++/ |
| D | NOTICE | 64 in supporting documentation. Hewlett-Packard Company makes no
76 in supporting documentation. Silicon Graphics makes no
|
| /bionic/libc/upstream-netbsd/libc/regex/ |
| D | regcomp.c | 1233 size_t no; in allocset() local
1242 no = p->g->ncsets++; in allocset()
1244 if (no >= p->ncsalloc) { /* need another column of space */ in allocset()
1260 for (i = 0; i < no; i++) in allocset()
1268 no = 0; in allocset()
1275 cs = &p->g->sets[no]; in allocset()
1276 cs->ptr = p->g->setbits + css*((no)/CHAR_BIT); in allocset()
1277 cs->mask = 1 << (unsigned int)((no) % CHAR_BIT); in allocset()
|
| /bionic/tests/ |
| D | Android.mk | 163 LOCAL_MODULE := no-elf-hash-table-library
|
| /bionic/libc/kernel/ |
| D | README.TXT | 167 functions. we consider it safe since userland applications have no business
260 headers (there is no reason to break the userland API for something
|