| /third_party/selinux/libselinux/src/ |
| D | file_path_suffixes.h | 3 S_(CONTEXTS_DIR, "/contexts")
4 S_(FILE_CONTEXTS, "/contexts/files/file_contexts")
5 S_(HOMEDIR_CONTEXTS, "/contexts/files/homedir_template")
6 S_(DEFAULT_CONTEXTS, "/contexts/default_contexts")
7 S_(USER_CONTEXTS, "/contexts/users/")
8 S_(FAILSAFE_CONTEXT, "/contexts/failsafe_context")
9 S_(DEFAULT_TYPE, "/contexts/default_type")
10 S_(SECURETTY_TYPES, "/contexts/securetty_types")
13 S_(MEDIA_CONTEXTS, "/contexts/files/media")
14 S_(REMOVABLE_CONTEXT, "/contexts/removable_context")
[all …]
|
| /third_party/typescript/tests/baselines/reference/ |
| D | varBlock.errors.txt | 1 …s/cases/compiler/varBlock.ts(8,18): error TS1039: Initializers are not allowed in ambient contexts.
4 …/cases/compiler/varBlock.ts(15,17): error TS1039: Initializers are not allowed in ambient contexts.
5 …/cases/compiler/varBlock.ts(21,18): error TS1039: Initializers are not allowed in ambient contexts.
6 …/cases/compiler/varBlock.ts(22,22): error TS1039: Initializers are not allowed in ambient contexts.
7 …/cases/compiler/varBlock.ts(25,21): error TS1039: Initializers are not allowed in ambient contexts.
8 …/cases/compiler/varBlock.ts(26,26): error TS1039: Initializers are not allowed in ambient contexts.
9 …/cases/compiler/varBlock.ts(26,35): error TS1039: Initializers are not allowed in ambient contexts.
10 …/cases/compiler/varBlock.ts(27,29): error TS1039: Initializers are not allowed in ambient contexts.
11 …/cases/compiler/varBlock.ts(28,35): error TS1039: Initializers are not allowed in ambient contexts.
12 …/cases/compiler/varBlock.ts(28,45): error TS1039: Initializers are not allowed in ambient contexts.
[all …]
|
| D | accessorsInAmbientContext.errors.txt | 1 …sInAmbientContext.ts(3,17): error TS1183: An implementation cannot be declared in ambient contexts.
2 …sInAmbientContext.ts(4,18): error TS1183: An implementation cannot be declared in ambient contexts.
3 …sInAmbientContext.ts(6,24): error TS1183: An implementation cannot be declared in ambient contexts.
4 …sInAmbientContext.ts(7,25): error TS1183: An implementation cannot be declared in ambient contexts.
5 …InAmbientContext.ts(12,13): error TS1183: An implementation cannot be declared in ambient contexts.
6 …InAmbientContext.ts(13,14): error TS1183: An implementation cannot be declared in ambient contexts.
7 …InAmbientContext.ts(15,20): error TS1183: An implementation cannot be declared in ambient contexts.
8 …InAmbientContext.ts(16,21): error TS1183: An implementation cannot be declared in ambient contexts.
16 !!! error TS1183: An implementation cannot be declared in ambient contexts.
19 !!! error TS1183: An implementation cannot be declared in ambient contexts.
[all …]
|
| D | initializersInDeclarations.errors.txt | 1 …ce/externalModules/file1.d.ts(4,9): error TS1039: Initializers are not allowed in ambient contexts.
2 …e/externalModules/file1.d.ts(5,16): error TS1039: Initializers are not allowed in ambient contexts.
3 …alModules/file1.d.ts(6,16): error TS1183: An implementation cannot be declared in ambient contexts.
4 …/externalModules/file1.d.ts(11,17): error TS1039: Initializers are not allowed in ambient contexts.
5 …/externalModules/file1.d.ts(12,17): error TS1039: Initializers are not allowed in ambient contexts.
6 …nce/externalModules/file1.d.ts(15,2): error TS1036: Statements are not allowed in ambient contexts.
7 …/externalModules/file1.d.ts(17,18): error TS1039: Initializers are not allowed in ambient contexts.
16 !!! error TS1039: Initializers are not allowed in ambient contexts.
19 !!! error TS1039: Initializers are not allowed in ambient contexts.
22 !!! error TS1183: An implementation cannot be declared in ambient contexts.
[all …]
|
| D | ambientErrors.errors.txt | 1 …nce/ambient/ambientErrors.ts(2,17): error TS1039: Initializers are not allowed in ambient contexts.
3 …nt/ambientErrors.ts(20,24): error TS1183: An implementation cannot be declared in ambient contexts.
5 …ce/ambient/ambientErrors.ts(34,13): error TS1039: Initializers are not allowed in ambient contexts.
6 …nt/ambientErrors.ts(35,19): error TS1183: An implementation cannot be declared in ambient contexts.
7 …ce/ambient/ambientErrors.ts(37,20): error TS1039: Initializers are not allowed in ambient contexts.
8 …ce/ambient/ambientErrors.ts(38,13): error TS1039: Initializers are not allowed in ambient contexts.
9 …nt/ambientErrors.ts(39,23): error TS1183: An implementation cannot be declared in ambient contexts.
10 …nt/ambientErrors.ts(40,14): error TS1183: An implementation cannot be declared in ambient contexts.
11 …nt/ambientErrors.ts(41,22): error TS1183: An implementation cannot be declared in ambient contexts.
21 !!! error TS1039: Initializers are not allowed in ambient contexts.
[all …]
|
| D | constDeclarations-ambient-errors.errors.txt | 1 …clarations-ambient-errors.ts(2,29): error TS1039: Initializers are not allowed in ambient contexts.
2 …clarations-ambient-errors.ts(3,28): error TS1039: Initializers are not allowed in ambient contexts.
4 …clarations-ambient-errors.ts(4,39): error TS1039: Initializers are not allowed in ambient contexts.
5 …clarations-ambient-errors.ts(4,53): error TS1039: Initializers are not allowed in ambient contexts.
6 …clarations-ambient-errors.ts(8,24): error TS1039: Initializers are not allowed in ambient contexts.
13 !!! error TS1039: Initializers are not allowed in ambient contexts.
16 !!! error TS1039: Initializers are not allowed in ambient contexts.
21 !!! error TS1039: Initializers are not allowed in ambient contexts.
23 !!! error TS1039: Initializers are not allowed in ambient contexts.
29 !!! error TS1039: Initializers are not allowed in ambient contexts.
|
| D | giant.errors.txt | 47 …/compiler/giant.ts(153,39): error TS1183: An implementation cannot be declared in ambient contexts.
71 …/compiler/giant.ts(232,39): error TS1183: An implementation cannot be declared in ambient contexts.
72 …/compiler/giant.ts(237,35): error TS1183: An implementation cannot be declared in ambient contexts.
73 …/compiler/giant.ts(239,24): error TS1183: An implementation cannot be declared in ambient contexts.
74 …/compiler/giant.ts(242,21): error TS1183: An implementation cannot be declared in ambient contexts.
75 …/compiler/giant.ts(243,22): error TS1183: An implementation cannot be declared in ambient contexts.
77 …/compiler/giant.ts(244,22): error TS1183: An implementation cannot be declared in ambient contexts.
80 …/compiler/giant.ts(246,31): error TS1183: An implementation cannot be declared in ambient contexts.
83 …/compiler/giant.ts(248,23): error TS1183: An implementation cannot be declared in ambient contexts.
86 …/compiler/giant.ts(250,32): error TS1183: An implementation cannot be declared in ambient contexts.
[all …]
|
| D | accessorBodyInTypeContext.errors.txt | 1 …BodyInTypeContext.ts(2,15): error TS1183: An implementation cannot be declared in ambient contexts.
2 …BodyInTypeContext.ts(6,21): error TS1183: An implementation cannot be declared in ambient contexts.
3 …odyInTypeContext.ts(10,15): error TS1183: An implementation cannot be declared in ambient contexts.
4 …odyInTypeContext.ts(14,21): error TS1183: An implementation cannot be declared in ambient contexts.
11 !!! error TS1183: An implementation cannot be declared in ambient contexts.
17 !!! error TS1183: An implementation cannot be declared in ambient contexts.
23 !!! error TS1183: An implementation cannot be declared in ambient contexts.
29 !!! error TS1183: An implementation cannot be declared in ambient contexts.
|
| /third_party/selinux/libselinux/man/man3/ |
| D | selinux_file_context_verify.3 | 3 … security context on disk to the default security context required by the policy file contexts file
14 …(in the extended attribute), to the system default entry held in the file contexts series of files.
20 Note that the two contexts are compared for "significant" differences (i.e. the user component of t…
25 If the contexts significantly match, 1 (one) is returned.
27 If the contexts do not match 0 (zero) is returned and
37 = 0 then the contexts did not match.
49 if there is no entry in the file contexts series of files or
54 if the entry in the file contexts series of files or
62 The following configuration files (the file contexts series of files) supporting the active policy …
67 .I contexts/files/file_contexts
[all …]
|
| D | get_ordered_context_list.3 | 31 all reachable security contexts for a given SELinux user or a single default
45 obtains the list of contexts for the specified
51 .I \%/etc/selinux/{SELINUXTYPE}/contexts/default_contexts
53 .I \%/etc/selinux/{SELINUXTYPE}/contexts/users/<username>
57 be used. The function returns the number of contexts in the
91 takes a list of contexts, queries the user via stdin/stdout as to which context
98 authorized contexts could not be obtained. Caller must free via
112 return the number of contexts in the list upon success or \-1 upon errors.
|
| /third_party/selinux/libselinux/man/man5/ |
| D | selabel_file.5 | 6 …\- userspace SELinux labeling interface and configuration file format for the file contexts backend
25 The file contexts backend maps from pathname/mode combinations into security contexts. It is used t…
27 … error codes, however the following \fIerrno\fR is clarified further for the file contexts backend:
31 …\fR and \fImode\fR was found - This will also be returned when the file contexts series of files h…
52 …ifies a path to a file that will be opened in lieu of the standard file contexts file. This value…
55 A non-null value for this option indicates that any local customizations to the file contexts mappi…
64 …the \fBSELABEL_OPT_PATH\fR value will default to the active policy file contexts location (as retu…
69 The mandatory file contexts file that is either the fully qualified file name from \fISELABEL_OPT_P…
71 …substitution files that perform path aliasing on the 'in memory' version of the file contexts file.
73 These files have the same name as the mandatory file contexts file with the extensions \fI.subs\fR …
[all …]
|
| D | selabel_media.5 | 6 …- userspace SELinux labeling interface and configuration file format for the media contexts backend
25 The media contexts backend maps from media device names such as "cdrom" or "floppy" into security c…
44 …n specifies a path to a file that will be opened in lieu of the standard \fImedia\fR contexts file.
47 …he \fBSELABEL_OPT_PATH\fR value will default to the active policy media contexts location (as retu…
49 The default media contexts file is:
51 .I /etc/selinux/{SELINUXTYPE}/contexts/files/media
76 # contexts/files/media
85 If contexts are to be validated, then the global option \fBSELABEL_OPT_VALIDATE\fR must be set befo…
|
| D | selabel_db.5 | 25 The DB contexts backend maps from a pair of object name and class into security contexts. It is use…
67 …blic.my_func". Note that we don't support lookup of individual security contexts for procedures wh…
115 …his option specifies a path to a file that will be opened in lieu of the standard DB contexts file.
120 …\fBSELABEL_OPT_PATH\fR value will default to the active policy database contexts location (as retu…
122 The default database object contexts file is:
124 .I /etc/selinux/{SELINUXTYPE}/contexts/sepgsql_context
129 The entries within the database contexts file are shown in the \fBObject Name String Values\fR and …
132 … assigned to each \fIobject_type\fR argument that can be present in the database contexts file are:
153 Each line within the database contexts file is as follows:
180 # ./contexts/sepgsql_contexts file
[all …]
|
| D | selabel_x.5 | 6 …abeling interface and configuration file format for the X Window System contexts backend. This bac…
25 The X contexts backend maps from X Window System object names into security contexts. It is used to…
57 …select the default entry) or a specific entry such as "remote" in the X contexts file as shown in …
82 …pecifies a path to a file that will be opened in lieu of the standard X contexts file (see the \fB…
86 …en the \fBSELABEL_OPT_PATH\fR value will default to the active policy X contexts location (as retu…
88 The default X object contexts file is:
90 .I /etc/selinux/{SELINUXTYPE}/contexts/x_contexts
95 The entries within the X contexts file are shown in the \fBObject Name String Values\fR and \fBFILE…
98 The string name assigned to each \fIobject_type\fR argument that can be present in the X contexts f…
114 Each line within the X contexts file is as follows:
[all …]
|
| /third_party/vk-gl-cts/modules/egl/ |
| D | teglMultiContextTests.cpp | 135 std::vector<eglw::EGLContext> contexts; in iterate() local
138 contexts.reserve(maxContextCount); in iterate()
140 …maxContextCount << (m_sharing == SHARING_SHARED ? " shared " : " ") << "contexts." << TestLog::End… in iterate()
141 …log << TestLog::Message << "Requiring that at least " << minContextCount << " contexts can be crea… in iterate()
152 …text sharedContext = (m_sharing == SHARING_SHARED && contextCount > 0 ? contexts[rng.getUint32() %… in iterate()
158 …log << TestLog::Message << "Got error after creating " << contextCount << " contexts." << TestLog:… in iterate()
163 resultCollector.fail("Couldn't create the minimum number of contexts required."); in iterate()
177 contexts.push_back(context); in iterate()
202 for (size_t contextNdx = 0; contextNdx < contexts.size(); contextNdx++) in iterate()
204 EGLU_CHECK_CALL(egl, destroyContext(*display, contexts[contextNdx])); in iterate()
[all …]
|
| /third_party/skia/third_party/externals/opengl-registry/extensions/EXT/ |
| D | GLX_EXT_no_config_context.txt | 56 creating OpenGL or OpenGL ES contexts supporting specific versions or
62 Modern GPUs allow contexts to render to almost any combination of
65 and constrains contexts to only work with drawables created with a
68 This extension allows creation of GL & ES contexts without specifying a
91 In section 2.1 "Rendering Contexts and Drawing Surfaces", modify the
108 Append a new paragraph to the end of section 2.1 "Rendering Contexts
118 versions of OpenGL. Such contexts are compatible with any drawable on the
120 further restrictions. For example, forward-compatible OpenGL 3.0 contexts
124 In section 3.3.7 "Rendering Contexts" in the discussion of glXQueryContext,
158 1) Should non-conformant no-config contexts be allowed to be created?
[all …]
|
| /third_party/openGLES/extensions/EXT/ |
| D | GLX_EXT_no_config_context.txt | 60 creating OpenGL or OpenGL ES contexts supporting specific versions or
66 Modern GPUs allow contexts to render to almost any combination of
69 and constrains contexts to only work with drawables created with a
72 This extension allows creation of GL & ES contexts without specifying a
95 In section 2.1 "Rendering Contexts and Drawing Surfaces", modify the
112 Append a new paragraph to the end of section 2.1 "Rendering Contexts
122 versions of OpenGL. Such contexts are compatible with any drawable on the
124 further restrictions. For example, forward-compatible OpenGL 3.0 contexts
128 In section 3.3.7 "Rendering Contexts" in the discussion of glXQueryContext,
162 1) Should non-conformant no-config contexts be allowed to be created?
[all …]
|
| /third_party/skia/third_party/externals/angle2/src/tests/gl_tests/ |
| D | TimerQueriesTest.cpp | 277 // Tests timer queries operating under multiple EGL contexts with mid-query switching
290 // contexts. in TEST_P()
338 ContextInfo contexts[2]; in TEST_P() local
359 contexts[0].context = eglCreateContext(display, config, EGL_NO_CONTEXT, contextAttributes); in TEST_P()
360 contexts[0].display = display; in TEST_P()
361 ASSERT_NE(contexts[0].context, EGL_NO_CONTEXT); in TEST_P()
362 eglMakeCurrent(display, surface, surface, contexts[0].context); in TEST_P()
363 contexts[0].program = CompileProgram(essl1_shaders::vs::Simple(), essl1_shaders::fs::Red()); in TEST_P()
364 glGenQueriesEXT(1, &contexts[0].query); in TEST_P()
368 contexts[1].context = eglCreateContext(display, config, EGL_NO_CONTEXT, contextAttributes); in TEST_P()
[all …]
|
| /third_party/openGLES/extensions/ARB/ |
| D | WGL_ARB_create_context.txt | 122 all other contexts <hshareContext> already shares with, and the
123 newly created context. An arbitrary number of contexts can share
207 contexts are intended for use during application development, and
210 additional functionality provided by debug contexts may vary
214 required features of debug contexts.]
218 created. Forward-compatible contexts are defined only for OpenGL
239 contexts may only be requested for OpenGL 3.0 and above. Thus,
248 Because the purpose of forward-compatible contexts is to allow
268 contexts providing the requested API major and minor version,
275 one referenced by <hDC>, or if the contexts are otherwise
[all …]
|
| /third_party/skia/third_party/externals/opengl-registry/extensions/ARB/ |
| D | WGL_ARB_create_context.txt | 112 all other contexts <hshareContext> already shares with, and the
113 newly created context. An arbitrary number of contexts can share
197 contexts are intended for use during application development, and
200 additional functionality provided by debug contexts may vary
204 required features of debug contexts.]
208 created. Forward-compatible contexts are defined only for OpenGL
229 contexts may only be requested for OpenGL 3.0 and above. Thus,
238 Because the purpose of forward-compatible contexts is to allow
258 contexts providing the requested API major and minor version,
265 one referenced by <hDC>, or if the contexts are otherwise
[all …]
|
| /third_party/skia/third_party/externals/egl-registry/extensions/KHR/ |
| D | EGL_KHR_create_context.txt | 40 OpenGL and OpenGL ES contexts supporting specific versions, specific
56 advertise support for creating OpenGL ES 3.0 contexts.
119 Modify section 3.7 "Rendering Contexts" in the paragraph near
126 Replace section 3.7.1 "Creating Rendering Contexts" from the
141 version. They are only meaningful for OpenGL and OpenGL ES contexts,
142 and specifying them for other types of contexts will generate an
217 meaningful for OpenGL contexts, and specifying it for other types of
218 contexts, including OpenGL ES contexts, will generate an error.
248 certain types of contexts, as described for each bit below, and
254 contexts are intended for use during application development, to
[all …]
|
| D | EGL_KHR_no_config_context.txt | 53 creating OpenGL or OpenGL ES contexts supporting specific versions or
59 Modern GPUs allow contexts to render to almost any combination of
62 and constrains contexts to only work with surfaces created with a
65 This extension allows creation of GL & ES contexts without specifying an
80 Modify the 3rd paragraph of section 2.2 "Rendering Contexts and
83 "Surfaces and contexts are both created with respect to an EGLConfig.
98 * The context was created without an EGLConfig. Such contexts match
113 Rendering Contexts" on p. 51:
169 1) Should non-conformant no-config contexts be allowed to be created?
171 RESOLVED: No. We are not encouraging non-conformant contexts.
[all …]
|
| /third_party/EGL/extensions/KHR/ |
| D | EGL_KHR_create_context.txt | 40 OpenGL and OpenGL ES contexts supporting specific versions, specific
56 advertise support for creating OpenGL ES 3.0 contexts.
119 Modify section 3.7 "Rendering Contexts" in the paragraph near
126 Replace section 3.7.1 "Creating Rendering Contexts" from the
141 version. They are only meaningful for OpenGL and OpenGL ES contexts,
142 and specifying them for other types of contexts will generate an
217 meaningful for OpenGL contexts, and specifying it for other types of
218 contexts, including OpenGL ES contexts, will generate an error.
248 certain types of contexts, as described for each bit below, and
254 contexts are intended for use during application development, to
[all …]
|
| D | EGL_KHR_no_config_context.txt | 53 creating OpenGL or OpenGL ES contexts supporting specific versions or
59 Modern GPUs allow contexts to render to almost any combination of
62 and constrains contexts to only work with surfaces created with a
65 This extension allows creation of GL & ES contexts without specifying an
80 Modify the 3rd paragraph of section 2.2 "Rendering Contexts and
83 "Surfaces and contexts are both created with respect to an EGLConfig.
98 * The context was created without an EGLConfig. Such contexts match
113 Rendering Contexts" on p. 51:
169 1) Should non-conformant no-config contexts be allowed to be created?
171 RESOLVED: No. We are not encouraging non-conformant contexts.
[all …]
|
| /third_party/mesa3d/docs/_extra/specs/OLD/ |
| D | MESA_multithread_makecurrent.spec | 37 For some applications, maintaining per-thread contexts and
66 Replace the following sentence from section 2.2 Rendering Contexts:
78 Replace the following sentence from section 3.3.7 Rendering Contexts:
85 Replace the following sentence from section 3.5 Rendering Contexts:
94 None. The GLX extension only extends to direct rendering contexts.
133 (5) What requirements should be placed on the user managing contexts
143 share in synchronization for binding of their own contexts, so the
144 refcounting of the contexts is required to be threadsafe.
146 (6) Does this apply to indirect contexts?
149 for indirect contexts is left as-is.
|