Home
last modified time | relevance | path

Searched refs:standard (Results 1 – 25 of 858) sorted by relevance

12345678910>>...35

/external/icu4c/test/cintltst/
Dstdnmtst.c38 static int dotestname(const char *name, const char *standard, const char *expected) { in dotestname() argument
45 tag = ucnv_getStandardName(name, standard, &error); in dotestname()
47 log_err_status(error, "FAIL: could not find %s standard name for %s\n", standard, name); in dotestname()
50 … log_err("FAIL: expected %s for %s standard name for %s, got %s\n", expected, standard, name, tag); in dotestname()
66 const char *standard; in TestStandardName() local
69 standard = ucnv_getStandard(i, &err); in TestStandardName()
73 } else if (!standard || !*standard) { in TestStandardName()
74 log_err("FAIL: %s standard name at index %d\n", (standard ? "empty" : in TestStandardName()
114 static int dotestconv(const char *name, const char *standard, const char *expected) { in dotestconv() argument
121 tag = ucnv_getCanonicalName(name, standard, &error); in dotestconv()
[all …]
/external/icu4c/data/zone/
Dit.txt278 ls{"Ora standard dell'Africa occidentale"}
283 ls{"Ora standard Alaska"}
288 ls{"Ora standard dell'Amazzonia"}
293 ls{"Ora standard centrale USA"}
298 ls{"Ora standard orientale USA"}
303 ls{"Ora standard sulle Montagne Rocciose USA"}
308 ls{"Ora standard della costa del Pacifico USA"}
313 ls{"Ora standard di Anadyr"}
318 ls{"Ora standard araba"}
323 ls{"Ora standard dell'Argentina"}
[all …]
Dro.txt349 ls{"Ora standard Acre"}
366 ls{"Ora standard Africii Occidentale"}
371 ls{"Ora standard Alaska"}
376 ls{"Ora standard Alaska-Hawaii"}
381 ls{"Ora standard a Amazonului"}
386 ls{"Ora standard centrală"}
391 ls{"Ora standard orientală"}
396 ls{"Ora standard în zona montană"}
401 ls{"Ora standard în zona Pacific"}
406 ls{"Ora standard din Anadyr"}
[all …]
/external/hyphenation/
DREADME.nonstandard1 Non-standard hyphenation
4 Some languages use non-standard hyphenation; `discretionary'
13 non-standard hyphenation patterns. For example:
32 Unfortunatelly, now the conversion step can generate bad non-standard
33 patterns (non-standard -> standard pattern conversion), so using
36 patterns resulting bad non-standard hyphenation in a few cases. Using narrow
39 Syntax of the non-standard hyphenation patterns
72 - only the greater value guarantees the win (don't mix non-standard and
73 non-standard patterns with the same value, for example
96 There hasn't been extended PatGen pattern generator for non-standard
[all …]
/external/llvm/docs/CommandGuide/
Dllvm-as.rst14 into a file or to standard output.
17 standard input.
20 **llvm-as** sends its output to a file or standard output by following
23 * If the input is standard input, then the output is standard output.
45 sends its output to standard output.
Dllvm-dis.rst20 input from standard input.
22 If the input is being read from standard input, then **llvm-dis**
23 will send its output to standard output by default. Otherwise, the
52 to standard output.
Dopt.rst19 of the input source. It will usually print the results on standard output, but
20 in a few cases, it will print output to standard error or generate a file with
31 reads its input from standard input. Inputs can be in either the LLVM assembly
35 :program:`opt` writes its output to the standard output.
67 This is short hand for a standard list of *compile time optimization* passes.
79 simply removes the inlining pass from the standard list.
113 Record the amount of time needed for each pass and print it to standard
Dllvm-extract.rst24 The **llvm-extract** command reads its input from standard input if filename is
25 omitted or if filename is -. The output is always written to standard output,
81 **llvm-extract** sends its output to standard output.
/external/fdlibm/
Dreadme32 3. Compiler failure on non-standard code
35 are not standard C and cause some optimizing compilers (e.g. GCC)
118 create a multi-standard compliant FDLIBM. In this case, each
119 function in FDLIBM is actually a standard compliant wrapper
149 function to comply to the standard specified by the value
162 multi-standard compliant (supports IEEE,XOPEN,POSIX/ANSI,SVID).
169 To create a multi-standard compliant libm, use
170 make "CFLAGS = -D_IEEE_MODE" --- multi-standard fdlibm: default
172 make "CFLAGS = -D_XOPEN_MODE" --- multi-standard fdlibm: default
174 make "CFLAGS = -D_POSIX_MODE" --- multi-standard fdlibm: default
[all …]
/external/eigen/cmake/
DFindStandardMathLibrary.cmake1 # - Try to find how to link to the standard math library, if anything at all is needed to do.
6 # STANDARD_MATH_LIBRARY_FOUND - we found how to successfully link to the standard math library
7 # STANDARD_MATH_LIBRARY - the name of the standard library that one has to link to.
44 # standard name 'm' for the standard math library.
/external/chromium/chrome/browser/ui/cocoa/
Dstyled_text_field_unittest.mm125 // the standard focusing machinery, or by -resetFieldEditorFrameIfNeeded.
127 // Capture the editor frame resulting from the standard focus machinery.
140 // in the same frame as the standard focus machinery.
147 // the standard focusing machinery, or by -resetFieldEditorFrameIfNeeded.
155 // Capture the editor frame resulting from the standard focus machinery.
166 // result in the same frame as the standard focus machinery.
173 // the standard focusing machinery, or by -resetFieldEditorFrameIfNeeded.
181 // Capture the editor frame resulting from the standard focus machinery.
192 // result in the same frame as the standard focus machinery.
/external/linux-tools-perf/Documentation/
Dperf-help.txt17 on the standard output.
20 printed on the standard output.
33 Prints all the available commands on the standard output. This
/external/valgrind/main/docs/internals/
Dwhy-no-libc.txt5 Subject: Re: [Valgrind-developers] Using standard C library in valgrind tool
10 IS> I would like to write a valgrind tool that uses the standard c
34 that are the reason Valgrind tools don't link with the standard
45 thread-local storage (which I think is standard these days). Glibc now
57 So if you need C standard library functionality that isn't covered by
58 the Valgrind core's somewhat non-standard subset, you'll have to get
/external/libvpx/libvpx/nestegg/halloc/
DREADME4 Hierarchical memory heap interface - an extension to standard
28 * improved standard compliance thanks to the feedback
32 array, which happened to be common, but non-standard
/external/icu4c/data/coll/
Droot.txt16 default{"standard"}
72 standard{
/external/qemu/distrib/sdl-1.2.15/src/video/Xext/
DREADME2 The reason these libraries are built outside of the standard XFree86
7 Linux platforms. Since these libraries haven't become standard yet,
/external/zlib/src/contrib/iostream3/
DREADME15 The new classes are as standard-compliant as possible, closely following the
16 approach of the standard library's fstream classes. It compiles under gcc versions
17 3.2 and 3.3, but not under gcc 2.xx. This is mainly due to changes in the standard
/external/icu4c/tools/gencnval/
Dgencnval.c166 addAlias(const char *alias, uint16_t standard, uint16_t converter, UBool defaultName);
655 addAlias(const char *alias, uint16_t standard, uint16_t converter, UBool defaultName) { in addAlias() argument
660 if(standard>=MAX_TAG_COUNT) { in addAlias()
668 aliasList = &tags[standard].aliasList[converter]; in addAlias()
682 if (standard == ALL_TAG_NUM && GET_ALIAS_STR(converters[converter].converter) != alias) { in addAlias()
698 if (standard != ALL_TAG_NUM) { in addAlias()
701 for (idx2 = 0; idx2 < tags[standard].aliasList[idx].aliasCount; idx2++) { in addAlias()
702 uint16_t aliasNum = tags[standard].aliasList[idx].aliases[idx2]; in addAlias()
715 GET_TAG_STR(tags[standard].tag), in addAlias()
721 GET_TAG_STR(tags[standard].tag), in addAlias()
[all …]
/external/llvm/test/Transforms/SimplifyCFG/
Dvolatile-phioper.ll7 ; it can no longer use language standard as an excuse. The compiler
44 attributes #0 = { nounwind ssp uwtable "fp-contract-model"="standard" "no-frame-pointer-elim" "no-f…
45 attributes #1 = { "fp-contract-model"="standard" "no-frame-pointer-elim" "no-frame-pointer-elim-non…
/external/antlr/antlr-3.4/runtime/C/doxygen/
Datsections.dox59 /// compile correctly on any standard C compiler (assuming, of course, that you type in valid C cod…
89 /// the code they encapsulate to be placed in the generated .h file, \b after the standard
93 /// statement to cause your grammar code to include some standard definitions. Because you
116 /// the code they encapsulate to be placed in the generated .h file, \b before the standard
120 /// in the code before the standard ANTLR runtime includes defined them. This allows you
130 /// file (which includes the standard ANTLR3C library includes.
133 /// generated include and by the standard ANTLR3 includes. This is a good place to <code>\#undef</c…
/external/stlport/etc/
DSTLport-4.6.spec3 Summary: Complete C++ standard library
23 Summary: Complete C++ standard library header files and libraries
29 C++ standard library, including <complex> and SGI STL iostreams. If you
DSTLport-4.5.3.spec3 Summary: Complete C++ standard library
23 Summary: Complete C++ standard library header files and libraries
29 C++ standard library, including <complex> and SGI STL iostreams. If you
DSTLport-4.5.1.spec3 Summary: Complete C++ standard library
23 Summary: Complete C++ standard library header files and libraries
29 C++ standard library, including <complex> and SGI STL iostreams. If you
/external/antlr/antlr-3.4/antlr3-maven-plugin/src/site/apt/
Dindex.apt15 The job of the plugin is essentially to tell the standard ANTLR parser generator where the
39 As with all Maven plugins, this plugin will automatically default to standard locations
40 for your grammar and import files. Organizing your source code to reflect this standard
41 layout will greatly reduce the configuration effort required. The standard layout lookd
/external/clang/include/clang/Frontend/
DLangStandards.def16 /// \param IDENT - The name of the standard as a C++ identifier.
17 /// \param NAME - The name of the standard.
18 /// \param DESC - A short description of the standard.
19 /// \param FEATURES - The standard features as flags, these are enums from the

12345678910>>...35