Searched refs:systems (Results 1 – 25 of 863) sorted by relevance
12345678910>>...35
/external/pcre/dist/doc/ |
D | pcre-config.txt | 28 architecture independent files (/usr on many systems, 29 /usr/local on some systems) to the standard output. 41 systems). 45 many systems). 49 many systems). 54 -lpcre on many systems). 59 (-lpcreposix -lpcre on many systems). 63 some -I options, but is blank on many systems). 69 many systems).
|
/external/chromium_org/ppapi/api/private/ |
D | ppb_isolated_file_system_private.idl | 18 * of isolated file systems. 22 /** Type for invalid file systems */ 24 /** Type for CRX file systems */ 26 /** Type for PluginPrivate file systems */
|
/external/llvm/test/Transforms/MergeFunc/ |
D | fold-weak.ll | 7 ; only apply on ELF systems and not Mach-O systems.
|
/external/oprofile/events/ppc64/power7/ |
D | events | 23 …up 1 pm_utilization) Processor Cycles gated by the run latch. Operating systems use the run latch… 27 …up 1 pm_utilization) Processor Cycles gated by the run latch. Operating systems use the run latch… 35 …(Group 2 pm_branch1) Processor Cycles gated by the run latch. Operating systems use the run latch… 43 …(Group 3 pm_branch2) Processor Cycles gated by the run latch. Operating systems use the run latch… 51 …(Group 4 pm_branch3) Processor Cycles gated by the run latch. Operating systems use the run latch… 59 …(Group 5 pm_branch4) Processor Cycles gated by the run latch. Operating systems use the run latch… 67 …(Group 6 pm_branch5) Processor Cycles gated by the run latch. Operating systems use the run latch… 75 …(Group 7 pm_branch6) Processor Cycles gated by the run latch. Operating systems use the run latch… 83 …(Group 8 pm_branch7) Processor Cycles gated by the run latch. Operating systems use the run latch… 91 …(Group 9 pm_branch8) Processor Cycles gated by the run latch. Operating systems use the run latch… [all …]
|
/external/bison/m4/ |
D | extensions.m4 | 2 # Enable extensions on systems that normally disable them. 31 # Enable extensions on systems that normally disable them, 74 /* Enable GNU extensions on systems that have them. */ 110 # Enable extensions on systems that normally disable them,
|
D | largefile.m4 | 1 # Enable large files on systems where this is not the default. 58 # http://www.unix-systems.org/version2/whatsnew/lfs20mar.html 106 # Enable large files on systems where this is implemented by Gnulib, not by the
|
/external/chromium_org/build/config/ |
D | crypto.gni | 17 # only do this when we're using OpenSSL on desktop Linux systems. For other 18 # systems (Mac/Win/Android) we use the system certificate features.
|
/external/chromium_org/third_party/tcmalloc/vendor/ |
D | README | 4 systems. See 64-BIT ISSUES, below. 13 tcmalloc functionality is available on all systems we've tested; see 52 The heap profiler is available on all unix-based systems we've tested; 101 The CPU profiler is available on all unix-based systems we've tested; 167 Perftools was developed and tested on x86 Linux systems, and it works 168 in its full generality only on those systems. However, we've 195 When compiling perftools on some old systems, like RedHat 8, you may 211 64-bit systems, which use the libunwind library to get stack-traces. 224 2) On x86-64 64-bit systems, while tcmalloc itself works fine, the 251 recognize these annotations; these systems should not see any
|
/external/e2fsprogs/debian/ |
D | uuid-dev.README.Debian | 9 systems, so for people trying to build e2fsprogs on Ubuntu systems,
|
D | control.in | 213 The ext2, ext3 and ext4 file systems are successors of the original ext 215 hard disks on Debian and other Linux systems. 218 that directly accesses extended file systems. Programs that use libext2fs 231 The ext2, ext3 and ext4 file systems are successors of the original ext 233 hard disks on Debian and other Linux systems. 251 The ext2, ext3 and ext4 file systems are successors of the original ext 253 hard disks on Debian and other Linux systems. 256 ext2/3/4-based file systems.
|
/external/valgrind/main/docs/internals/ |
D | multiple-architectures.txt | 7 Valgrind supports systems where binaries for more than one 10 - single-arch support on x86 and ppc32 systems 11 - dual-arch support on amd64 and ppc64 systems 20 dual-arch systems, the primary platform is amd64 and ppc64 23 On dual-arch systems, there is a 'secondary' target - x86 and ppc32 29 On single-arch systems, there is no secondary target.
|
/external/chromium_org/native_client_sdk/src/libraries/third_party/pthreads-win32/ |
D | README.chromium | 20 commonly as pthreads. A good number of modern operating systems include a 23 The trend is that most of these systems are slowly adopting the pthreads
|
/external/linux-tools-perf/perf-3.12.0/tools/perf/util/ |
D | trace-event-read.c | 322 int systems; in read_event_files() local 327 systems = read4(pevent); in read_event_files() 329 for (i = 0; i < systems; i++) { in read_event_files()
|
/external/dhcpcd/ |
D | README | 35 Some BSD systems do not allow the manipulation of automatically added subnet 38 BSD systems where this has been fixed are: 60 The configure program attempts to find hooks for systems you have installed.
|
/external/qemu/distrib/jpeg-6b/ |
D | jconfig.doc | 139 * of extended memory; on most other systems it's not as important. 144 * This is necessary on systems that distinguish text files from binary files, 145 * and is harmless on most systems that don't. If you have one of the rare 146 * systems that complains about the "b" spec, define this symbol.
|
/external/jpeg/ |
D | jconfig.doc | 139 * of extended memory; on most other systems it's not as important. 144 * This is necessary on systems that distinguish text files from binary files, 145 * and is harmless on most systems that don't. If you have one of the rare 146 * systems that complains about the "b" spec, define this symbol.
|
/external/chromium_org/third_party/icu/source/samples/csdet/ |
D | readme.txt | 28 … must be in the same directory as the executable, which is not the case by default on some systems. 56 Note: The name of the LD_LIBRARY_PATH variable is different on some systems.
|
/external/icu/icu4c/source/samples/csdet/ |
D | readme.txt | 28 … must be in the same directory as the executable, which is not the case by default on some systems. 56 Note: The name of the LD_LIBRARY_PATH variable is different on some systems.
|
/external/chromium_org/third_party/icu/source/samples/break/ |
D | readme.txt | 27 4. Run it (Warning: Be careful, 'break' is also a system command on many systems) 56 Note: The name of the LD_LIBRARY_PATH variable is different on some systems.
|
/external/icu/icu4c/source/samples/break/ |
D | readme.txt | 27 4. Run it (Warning: Be careful, 'break' is also a system command on many systems) 56 Note: The name of the LD_LIBRARY_PATH variable is different on some systems.
|
/external/chromium_org/components/os_crypt/ |
D | README | 3 On systems where available (currently Linux and Mac), this uses system
|
/external/markdown/docs/ |
D | command_line.txt | 15 you Python "Scripts" directory. Different systems require different methods to 33 * Some systems will automatically install the script on your path. Try it 36 * Other systems may maintain a separate "Scripts" directory which you
|
/external/clang/docs/ |
D | JSONCompilationDatabase.rst | 16 - Build systems are inherently change driven, so running multiple tools 18 the architecture of many build systems. 22 - Build systems are inherently sequential in the build graph, for
|
/external/pcre/dist/ |
D | NON-UNIX-USE | 1 Compiling PCRE on non-Unix systems
|
/external/icu/icu4c/source/samples/date/ |
D | readme.txt | 29 4. Run it (Warning: Be careful, 'date' is also a system command on many systems) 54 Note: The name of the LD_LIBRARY_PATH variable is different on some systems.
|
12345678910>>...35