| /external/pcre/dist2/testdata/ |
| D | testoutput18 | 1 # This set of tests is run only with the 8-bit library. It tests the POSIX
3 # not be run with JIT (which is not available for the POSIX interface).
11 ** Ignored with POSIX interface: auto_callout
15 ** Ignored with POSIX interface: find_limits
20 ** Ignored with POSIX interface: partial_hard
24 ** Ignored with POSIX interface: parens_nest_limit
27 ** Ignored with POSIX interface: allow_surrogate_escapes max_pattern_length
57 No match: POSIX code 17: match failed
68 No match: POSIX code 17: match failed
77 Failed: POSIX code 15: bad back reference at offset 6
[all …]
|
| D | testoutput19 | 1 # This set of tests is run only with the 8-bit library. It tests the POSIX
4 # POSIX interface).
15 No match: POSIX code 17: match failed
|
| /external/ltp/testcases/open_posix_testsuite/Documentation/ |
| D | COVERAGE.signals | 5 This document lists the items that will be tested for POSIX signals.
16 the POSIX Test Suite creators are listed below.
20 Tag - tag that applies to the function in the POSIX spec
21 Complexity - POSIX test suite owners' intuitions at complexity of the function
23 Recommended? - set to "NO" if the POSIX spec recomments using *other*
25 Priority - POSIX test suite owners' intuitions at priorities of these
67 - Any additional information listed in the POSIX System Interfaces document
69 - Any functional requirements listed in the POSIX Base Definitions document.
70 (ex. Testing that each signal listed in the POSIX Base Definitions
|
| D | HOWTO_Assertions | 30 ref - For reference document (generally a POSIX specification)
38 XBD# - POSIX Base Definitions document
39 XSH# - POSIX System Interfaces document
40 XCU# - POSIX Shell and Utilities document
41 XRAT# - POSIX Rationale document
58 the official POSIX Specs, then simply put in
62 pt:<POSIXtag> - If the assertion is taken from a POSIX specification and there
63 is a POSIX tag (pt) associated with it, the additional string
65 POSIX tag.
|
| D | HOWTO_FunctionalStressTest | 10 Functional tests test the behavior of functional areas of the POSIX*
11 specification. They do not relate directly to lines in the POSIX
19 taxed by excessively using the functional areas in the POSIX specification
20 or monitoring how the functional areas in the POSIX specification behave
30 Each of these are further subdivided into POSIX area (Timers, Semaphores,
33 Within the functional/<POSIX area> directory, you should create the
71 - create directories corresponding to POSIX chapters (see .1-1990 or
75 * POSIX (R) is a registered trademark of the IEEE
|
| D | HOWTO_BugReporting | 2 POSIX Test Test Suites.
5 POSIX Test Test Suites.
15 - Code under test that is targeted* for the POSIX Test Suite reporting.
29 4. If the code under test is compatible with another POSIX version (e.g.,
45 *targeted implementation = an implementation which POSIX Test Suite will
47 **Process for tracing a test case to previous POSIX specifications not
|
| D | HOWTO_ConformanceTest | 10 Conformance tests test conformance to the POSIX* specification. They test
23 definitions/ - This directory contains tests for each *.h file in the POSIX
27 POSIX spec. Tests are taken from the System Interfaces document.
62 Tests which the POSIX spec uses the words "may" or "implementation-defined"
90 * POSIX (R) is a registered trademark of the IEEE
|
| D | HOWTO_Coverage | 4 Every area of the POSIX spec that has tests written for it should be tracked by
16 Completion of POSIX Function Conformance Tests
18 There should be one line for each POSIX function included in this area of the
19 POSIX spec. The tests for these functions are currently found in the
47 the POSIX spec such as "Clocks & Timers (TMR)".
|
| D | HOWTO_Tagging | 4 Releases of the POSIX Test Suite will happen at defined (TBD) intervals.
29 M = Major release. The initial scope of the POSIX Test Suite corresponds
30 to M=1. That includes tests for all initially scoped POSIX areas (signals,
|
| /external/ltp/testcases/open_posix_testsuite/ |
| D | BUILD | 1 Build Notes for POSIX Test Suite
5 The POSIX Test Suite should be able to be run independently of any given
6 OS, so the OS-specific steps for configuring the POSIX Test Suite to run
36 POSIX message queues have been available in FreeBSD since 6.x. Please add:
56 POSIX semaphores have been available in FreeBSD since 5.x. Please add:
64 Notes for running POSIX Test Suite against Linux implementations of
65 POSIX functionality. (Note: If these implementations are accepted into
81 If LinuxThreads is the default POSIX thread implementation,
86 If NPTL is the default POSIX thread implementation, add '-lpthread' to LDLIBS.
108 POSIX Message Queue (Wronski/Benedyczak's implementation) has been
[all …]
|
| D | README | 3 1. Open POSIX* Test Suite Overview
13 1. Open POSIX* Test Suite Overview
16 The POSIX Test Suite is an open source test suite with the goal of
23 POSIX operating system.
35 - Enable assertion based traceability for conformance testing of POSIX
37 statements about our coverage of the POSIX specification.
74 HOWTO_DefinitionsTest - ideas behind testing POSIX header files
120 The Open POSIX Test Suite is not affiliated with the IEEE or The Open Group.
122 * POSIX (R) is a registered trademark of the IEEE
|
| D | NEWS | 13 …S is helping kernel, library and application developers and OSDs on their POSIX related work. Plea…
19 …4-29 cvs pull (NPTL enabled) and linux-2.6.5-mm6 kernel.It is noted that "POSIX Message Queues" ha…
22 POSIX Test Suite 1.4.0 includes more pthread conformance test cases. Now we have test cases coverin…
25 POSIX Test Suite test pass results available for [CVS pull 3-04-04, Kernel 2.6.1, libc-2004-02-15 a…
28 POSIX Test Suite test pass results available for [CVS pull 2-20-04, Kernel 2.6.1, libc-2004-02-01 a…
|
| D | QUICK-START | 7 No worries! Here's a quick doc to help you around POSIX** Test Suite.
45 POSIX* Test Suite project page: http://posixtest.sf.net
57 HOWTO_DefinitionsTest - ideas behind testing POSIX header files
62 ** POSIX (R) is a registered trademark of the IEEE
|
| /external/cldr/tools/java/org/unicode/cldr/util/data/ |
| D | etcetera | 11 # that cannot use POSIX TZ settings.
13 # Starting with POSIX 1003.1-2001, the entries below are all
15 # instead of TZ='Etc/GMT+4' one can use the POSIX setting TZ='<-04>+4'.
17 # Do not use a POSIX TZ setting like TZ='GMT+4', which is four hours
37 # Be consistent with POSIX TZ settings in the Zone names,
39 # POSIX has positive signs west of Greenwich, but many people expect
45 # Earlier incarnations of this package were not POSIX-compliant,
|
| /external/honggfuzz/docs/ |
| D | Android.md | 4 both ptrace() API and POSIX signals interface. When ptrace() API is enabled,
30 | **armeabi** | ptrace() API & POSIX signal interface |
31 | **armeabi-v7a** | ptrace() API & POSIX signal interface |
32 | **arm64-v8a** | ptrace() API & POSIX signal interface `*`|
33 | **x86** | ptrace() API & POSIX signal interface |
34 | **x86_64** | ptrace() API & POSIX signal interface |
120 _`1`) If false, POSIX signals interface is used instead of PTRACE API_
|
| /external/icu/icu4c/source/test/intltest/ |
| D | simplethread.cpp | 45 # undef POSIX
47 # define POSIX macro
49 # undef POSIX
64 #if defined(POSIX)
212 #if defined(POSIX)
|
| /external/ltp/testcases/open_posix_testsuite/functional/threads/ |
| D | README | 5 area defined by POSIX.
8 funtional area (somewhat like POSIX options), or by APIs.
18 the work of adding Robust Mutex to POSIX is still ongoing.
|
| /external/cldr/tools/java/org/unicode/cldr/util/ |
| D | Level.java | 19 public static final Level POSIX = BASIC; field in Level
56 return POSIX; in get()
102 return Level.POSIX; in fromLevel()
|
| /external/libexif/m4m/ |
| D | gp-check-shell-environment.m4 | 19 AC_MSG_CHECKING([for POSIX sh \$() command substitution])
29 * POSIX sh \$() command substition does not work with this shell.
38 * Run this configure script using a better (i.e. POSIX compliant) shell.
|
| /external/python/cpython2/Doc/library/ |
| D | shlex.rst | 35 in POSIX mode by default, but uses non-POSIX mode if the *posix* argument is
65 compatibility mode. When operating in POSIX mode, :class:`~shlex.shlex`
66 will try to be as close as possible to the POSIX shell parsing rules.
88 string (``''``) in non-POSIX mode, and ``None`` in POSIX mode).
185 Characters that will be considered as escape. This will be only used in POSIX
201 :attr:`escape`. This is only used in POSIX mode, and includes just ``'"'`` by
261 (``''``), in non-POSIX mode, and to ``None`` in POSIX mode.
271 When operating in non-POSIX mode, :class:`~shlex.shlex` will try to obey to the
294 When operating in POSIX mode, :class:`~shlex.shlex` will try to obey to the
|
| D | termios.rst | 2 :mod:`termios` --- POSIX style tty control
7 :synopsis: POSIX style tty control.
11 pair: POSIX; I/O control
14 This module provides an interface to the POSIX calls for tty I/O control. For a
16 page. It is only available for those Unix versions that support POSIX
|
| /external/python/cpython3/Doc/library/ |
| D | termios.rst | 1 :mod:`termios` --- POSIX style tty control
6 :synopsis: POSIX style tty control.
9 pair: POSIX; I/O control
14 This module provides an interface to the POSIX calls for tty I/O control. For a
16 page. It is only available for those Unix versions that support POSIX
|
| /external/libcap/ |
| D | METADATA | 2 description: "This is a library for getting and setting POSIX.1e (formerly POSIX 6) draft 15 capabi…
|
| /external/perfetto/debian/ |
| D | control | 14 Description: Performance instrumentation and logging for POSIX platforms
15 Perfetto is a performance instrumentation and logging framework for POSIX
|
| /external/libchrome/mojo/core/ |
| D | embedder_unittest.cc | 349 POSIX, enumerator
354 HandleType::MACH, HandleType::POSIX, HandleType::POSIX, HandleType::MACH,
366 if (type == HandleType::POSIX) { in TEST_F()
412 if (type == HandleType::POSIX) { in DEFINE_TEST_CLIENT_TEST_WITH_PIPE()
|