| /third_party/mesa3d/include/ |
| D | meson.build | 125 'CL/cl.h',
126 'CL/cl.hpp',
127 'CL/cl2.hpp',
128 'CL/cl_d3d10.h',
129 'CL/cl_d3d11.h',
130 'CL/cl_dx9_media_sharing.h',
131 'CL/cl_dx9_media_sharing_intel.h',
132 'CL/cl_egl.h',
133 'CL/cl_ext.h',
134 'CL/cl_ext_intel.h',
[all …]
|
| /third_party/flutter/skia/third_party/externals/wuffs/test/data/artificial/ |
| D | deflate-degenerate-huffman-unused.deflate.commentary.txt | 11 Decode the H-CL Huffman table (NumCLCodeLengths = 18). Recall the peculiar
22 The H-CL Huffman table is:
30 000008 0x0008 . 0xA0 0b_1..._.... "11" is CL=18: 11+7extra
33 000010 0x000A V 0x56 0b_...._..10 "01" is CL= 2 (102='f')
34 000010 0x000A V 0x56 0b_...._01.. "10" is CL=17: 3+3extra
36 000010 0x000A V 0x56 0b_0..._.... "00" is CL= 1 (111='o')
38 000011 0x000B . 0xFE 0b_...._.11. "11" is CL=18: 11+7extra
41 000012 0x000C 7 0x37 0b_...._01.. "10" is CL=17: 3+3extra
43 000012 0x000C 7 0x37 0b_0..._.... "01" is CL=2 (256=EOB)
53 000013 0x000D . 0x89 0b_...._.00. "00" is CL= 1 (DCode 0)
|
| /third_party/mesa3d/src/mesa/x86/ |
| D | x86_cliptest.S | 202 MOV_B( REGBI(EBP, ECX), CL )
204 MOV_B( REGOFF(clip_table,ECX), CL )
207 OR_B( CL, AL )
208 AND_B( CL, AH )
210 TEST_B( CL, CL )
211 MOV_B( CL, REGIND(EDX) )
368 MOV_B( REGBI(EBP, ECX), CL )
370 MOV_B( REGOFF(clip_table,ECX), CL )
373 OR_B( CL, AL )
374 AND_B( CL, AH )
[all …]
|
| /third_party/skia/third_party/externals/angle2/doc/ |
| D | CodeReviewProcess.md | 9 The author of a CL may designate reviewers. Please feel free to weigh in on
12 1. To review a change, you can either navigate directly to the URL for the CL,
22 that pre-exist the CL are not required to be addressed in the CL. As a
23 reviewer, you can request a follow-up CL to address the style issue if
39 reviewer to clear the CL.
44 * If the CL author is not an ANGLE committer, the CL should be verified
46 be added, and the CL may be landed with the "Publish and Submit" button.
49 * If the CL author is an ANGLE committer, they should verify and land the
50 CL themselves.
55 using the "Cherry Pick To" button on the CL page.
|
| D | ContributingCode.md | 131 CL with a particular review, and track dependencies between commits.
149 * Associate the CL with an issue in the issue tracker (e.g. a fix for a reported bug)
154 * Use `git commit --amend` to update your CL with new changes.
155 … * Use `git cl format` to amend the style of your CL. This saves both your time and the reviewers'!
178 7. Pull and integrate reviewed CL:
185 When your CL is ready to review, you can use the "Find Owners" button in
187 CL to additional reviewers as neccessary and answer any questions you may have
203 ### Reverting a CL
206 pre-submit testing. In those cases, a CL may be reverted; often by a "[Wrangler][wrangler]", who is
213 commit message, and an optional checkbox for automatically sending the revert CL to CQ. Please edit
[all …]
|
| D | TestingAndProcesses.md | 7 We run a large number of tests for each ANGLE CL, both in ANGLE standalone and Chromium
11 suppress failures immediately; where a developer will typically delay landing their CL in favor of
65 1. Add rubber-stamper@appspot.gserviceaccount.com as the reviewer on the expectations CL. Please al…
66 2. After 1 minute, Rubber Stamper should set "Bot-Commit: +1" on the CL.
67 3. Now you should be able to "Commit-Queue: +2" your CL.
84 You will need to contact an OWNER of the file to +1 your CL.
86 You have two options for creating a CL to the expectations files:
93 need to change your CL later), which will create a CL.
95 …and [upload a CL](https://chromium.googlesource.com/chromium/src/+/refs/heads/main/docs/contributi…
|
| /third_party/flutter/skia/third_party/externals/angle2/doc/ |
| D | CodeReviewProcess.md | 9 The author of a CL may designate reviewers. Please feel free to weigh in on
12 1. To review a change, you can either navigate directly to the URL for the CL,
22 that pre-exist the CL are not required to be addressed in the CL. As a
23 reviewer, you can request a follow-up CL to address the style issue if
39 reviewer to clear the CL.
44 * If the CL author is not an ANGLE committer, the CL should be verified
46 be added, and the CL may be landed with the "Publish and Submit" button.
49 * If the CL author is an ANGLE committer, they should verify and land the
50 CL themselves.
55 using the "Cherry Pick To" button on the CL page.
|
| /third_party/flutter/skia/site/dev/contrib/ |
| D | cqkeywords.md | 22 The CQ rejects patchsets with open dependencies. An open dependency exists when a CL
23 depends on another CL that is not yet closed. You can skip this check with this keyword.
45 If you want to skip the tree status checks, to make the CQ commit a CL even if the tree is closed,
46 you can add the following line to the CL description:
51 primarily to fix build breakages (i.e., your CL will help in reopening the tree).
56 If you want to skip the presubmit checks, add the following line to the CL description:
63 If you cannot wait for the try job results, you can add the following line to the CL description:
67 The CQ will then not run any try jobs for your change and will commit the CL as soon as the tree is…
|
| /third_party/skia/third_party/externals/swiftshader/third_party/llvm-10.0/llvm/lib/Target/X86/ |
| D | X86InstrShiftRotate.td | 18 let Uses = [CL], SchedRW = [WriteShiftCL] in {
21 [(set GR8:$dst, (shl GR8:$src1, CL))]>;
24 [(set GR16:$dst, (shl GR16:$src1, CL))]>, OpSize16;
27 [(set GR32:$dst, (shl GR32:$src1, CL))]>, OpSize32;
30 [(set GR64:$dst, (shl GR64:$src1, CL))]>;
31 } // Uses = [CL], SchedRW
66 // FIXME: Why do we need an explicit "Uses = [CL]" when the instr has a pattern
67 // using CL?
68 let Uses = [CL], SchedRW = [WriteShiftCLLd, WriteRMW] in {
71 [(store (shl (loadi8 addr:$dst), CL), addr:$dst)]>;
[all …]
|
| /third_party/skia/site/docs/dev/contrib/ |
| D | cqkeywords.md | 38 The CQ rejects patchsets with open dependencies. An open dependency exists when a CL
39 depends on another CL that is not yet closed. You can skip this check with this keyword.
71 If you want to skip the tree status checks, to make the CQ commit a CL even if
72 the tree is closed, you can add the following line to the CL description:
77 cases this is acceptable, primarily to fix build breakages (i.e., your CL will
84 If you want to skip the presubmit checks, add the following line to the CL description:
93 the CL description:
97 The CQ will then not run any try jobs for your change and will commit the CL as
|
| D | revert.md | 3 title: "How to revert a CL"
4 linkTitle: "How to revert a CL"
11 * Find the codereview issue for the CL you want to revert.
|
| /third_party/opencl-headers/ |
| D | README_zh.md | 17 CL/ 原CL头文件
18 include/ 封装层CL头文件
19 src/ 封装层CL实现
|
| /third_party/skia/third_party/externals/egl-registry/extensions/KHR/ |
| D | EGL_KHR_cl_event.txt | 96 "A <CL event sync object> reflects the status of a corresponding
101 equivalent to waiting for completion of the linked CL event object."
106 "If <type> is EGL_SYNC_CL_EVENT_KHR, a CL event sync object is
110 object. Attributes of the CL event sync objects are set as follows:
157 be deleted when the associated fence command or CL event object has
183 having a constructor specific to CL events. This was intended in the
198 4) Should all possible statuses of the CL event be reflected through to the
201 DISCUSSION: CL event objects have four execution statuses:
214 5) Are there any restrictions on the use of a sync object linked to a CL
221 RESOLVED: A sync object linked to a CL event object places a single
[all …]
|
| /third_party/EGL/extensions/KHR/ |
| D | EGL_KHR_cl_event.txt | 96 "A <CL event sync object> reflects the status of a corresponding
101 equivalent to waiting for completion of the linked CL event object."
106 "If <type> is EGL_SYNC_CL_EVENT_KHR, a CL event sync object is
110 object. Attributes of the CL event sync objects are set as follows:
157 be deleted when the associated fence command or CL event object has
183 having a constructor specific to CL events. This was intended in the
198 4) Should all possible statuses of the CL event be reflected through to the
201 DISCUSSION: CL event objects have four execution statuses:
214 5) Are there any restrictions on the use of a sync object linked to a CL
221 RESOLVED: A sync object linked to a CL event object places a single
[all …]
|
| /third_party/skia/site/docs/dev/testing/ |
| D | skiagold.md | 16 - Deviations from the baseline are triaged after a CL lands and images are
19 and requires a fix. If a CL causes Skia to break it is reverted or an
20 additional CL is landed to fix the problem.
79 ## Problem #2: As a developer, I need to land a CL that may change many images.
85 - Click on one of the clusters including your CL to triage
89 CL. Delete hashes in the URL to only include the hash for your CL.
113 - Trybot support prior to commit, with view limited to your CL
114 - Pre-triage prior to commit that will persist when the CL lands
|
| /third_party/flutter/skia/site/dev/testing/ |
| D | skiagold.md | 13 * Deviations from the baseline are triaged after a CL lands and images are
17 If a CL causes Skia to break it is reverted or an additional CL is landed to
73 Problem #2: As a developer, I need to land a CL that may change many images.
79 * Click on one of the clusters including your CL to triage
83 by CL. Delete hashes in the URL to only include the hash for your CL.
106 * Trybot support prior to commit, with view limited to your CL
107 * Pre-triage prior to commit that will persist when the CL lands
|
| /third_party/skia/third_party/externals/opengl-registry/extensions/ARB/ |
| D | ARB_cl_event.txt | 85 equivalent to waiting for completion of the linked CL event object.
247 could be used to pass the necessary CL event-specific parameters
248 (CL context and event handle), or a CL event-specific command
266 specifying an event interface using the CL cl_context and
268 there may be a dependency loop between CL and GL headers in
283 3) Should all possible statuses of the CL event be reflected through
286 DISCUSSION: CL event objects have four execution statuses:
296 4) What is the sync type of a sync object linked to a CL event?
301 created from a CL event is equivalent to a fence sync: it starts
306 RESOLVED: The OBJECT_TYPE of a GL sync object created from a CL
[all …]
|
| /third_party/openGLES/extensions/ARB/ |
| D | ARB_cl_event.txt | 95 equivalent to waiting for completion of the linked CL event object.
257 could be used to pass the necessary CL event-specific parameters
258 (CL context and event handle), or a CL event-specific command
276 specifying an event interface using the CL cl_context and
278 there may be a dependency loop between CL and GL headers in
293 3) Should all possible statuses of the CL event be reflected through
296 DISCUSSION: CL event objects have four execution statuses:
306 4) What is the sync type of a sync object linked to a CL event?
311 created from a CL event is equivalent to a fence sync: it starts
316 RESOLVED: The OBJECT_TYPE of a GL sync object created from a CL
[all …]
|
| /third_party/boost/libs/compute/cmake/opencl/ |
| D | FindOpenCL.cmake | 44 FIND_PATH(OpenCL_INCLUDE_DIRS CL/cl.h PATHS
46 FIND_PATH(_OpenCL_CPP_INCLUDE_DIRS CL/cl.hpp PATHS
62 …FIND_PATH(OpenCL_INCLUDE_DIRS CL/cl.h PATHS "$ENV{CUDADIR}/include" ${_OpenCL_INC_CAND} "/usr/loca…
63 …FIND_PATH(_OpenCL_CPP_INCLUDE_DIRS CL/cl.hpp PATHS "$ENV{CUDADIR}/include" ${_OpenCL_INC_CAND} "/u…
|
| /third_party/skia/third_party/externals/angle2/src/ |
| D | libGLESv2.gni | 450 "include/CL/cl.h",
451 "include/CL/cl_d3d10.h",
452 "include/CL/cl_d3d11.h",
453 "include/CL/cl_dx9_media_sharing.h",
454 "include/CL/cl_dx9_media_sharing_intel.h",
455 "include/CL/cl_egl.h",
456 "include/CL/cl_ext.h",
457 "include/CL/cl_ext_intel.h",
458 "include/CL/cl_gl.h",
459 "include/CL/cl_gl_ext.h",
[all …]
|
| /third_party/skia/third_party/externals/icu/source/data/brkitr/rules/ |
| D | line_cj.txt | 36 $CL = [[:LineBreak = Close_Punctuation:] \u201d];
119 $AL_FOLLOW = [$BK $CR $LF $NL $ZW $SP $CL $CP $EX $HL $IS $SY $WJ $GL $OP30 $QU $BA $HY $NS $I…
188 $LB8NonBreaks $CL;
189 $CAN_CM $CM* $CL;
190 ^$CM+ $CL; # by rule 10, stand-alone CM behaves as AL
222 $CanFollowIS = [$BK $CR $LF $NL $SP $ZW $WJ $GL $CL $CP $EX $IS $SY $QU $BA $HY $NS $ALPlus $HL $IN…
241 ($CL | $CP) $CM* $SP* $NS;
322 ($CM* ($CL | $CP))? ($CM* ($PR | $PO))?;
351 $RI $CM* $RI / [[^$BK $CR $LF $NL $SP $ZW $WJ $CL $CP $EX $IS $SY $GL $QU $BA $HY $…
352 $RI $CM* $RI $CM* [$CM-$ZWJ] / [[^$BK $CR $LF $NL $SP $ZW $WJ $CL $CP $EX $IS $SY $GL $QU $BA $HY $…
[all …]
|
| D | line_normal.txt | 37 $CL = [:LineBreak = Close_Punctuation:];
120 $AL_FOLLOW = [$BK $CR $LF $NL $ZW $SP $CL $CP $EX $HL $IS $SY $WJ $GL $OP30 $QU $BA $HY $NS $I…
189 $LB8NonBreaks $CL;
190 $CAN_CM $CM* $CL;
191 ^$CM+ $CL; # by rule 10, stand-alone CM behaves as AL
223 $CanFollowIS = [$BK $CR $LF $NL $SP $ZW $WJ $GL $CL $CP $EX $IS $SY $QU $BA $HY $NS $ALPlus $HL $IN…
242 ($CL | $CP) $CM* $SP* $NS;
323 ($CM* ($CL | $CP))? ($CM* ($PR | $PO))?;
352 $RI $CM* $RI / [[^$BK $CR $LF $NL $SP $ZW $WJ $CL $CP $EX $IS $SY $GL $QU $BA $HY $…
353 $RI $CM* $RI $CM* [$CM-$ZWJ] / [[^$BK $CR $LF $NL $SP $ZW $WJ $CL $CP $EX $IS $SY $GL $QU $BA $HY $…
[all …]
|
| /third_party/icu/icu4c/source/data/brkitr/rules/ |
| D | line_cj.txt | 36 $CL = [[:LineBreak = Close_Punctuation:] \u201d];
119 $AL_FOLLOW = [$BK $CR $LF $NL $ZW $SP $CL $CP $EX $HL $IS $SY $WJ $GL $OP30 $QU $BA $HY $NS $I…
188 $LB8NonBreaks $CL;
189 $CAN_CM $CM* $CL;
190 ^$CM+ $CL; # by rule 10, stand-alone CM behaves as AL
222 $CanFollowIS = [$BK $CR $LF $NL $SP $ZW $WJ $GL $CL $CP $EX $IS $SY $QU $BA $HY $NS $ALPlus $HL $IN…
241 ($CL | $CP) $CM* $SP* $NS;
322 ($CM* ($CL | $CP))? ($CM* ($PR | $PO))?;
351 $RI $CM* $RI / [[^$BK $CR $LF $NL $SP $ZW $WJ $CL $CP $EX $IS $SY $GL $QU $BA $HY $…
352 $RI $CM* $RI $CM* [$CM-$ZWJ] / [[^$BK $CR $LF $NL $SP $ZW $WJ $CL $CP $EX $IS $SY $GL $QU $BA $HY $…
[all …]
|
| D | line_normal.txt | 37 $CL = [:LineBreak = Close_Punctuation:];
120 $AL_FOLLOW = [$BK $CR $LF $NL $ZW $SP $CL $CP $EX $HL $IS $SY $WJ $GL $OP30 $QU $BA $HY $NS $I…
189 $LB8NonBreaks $CL;
190 $CAN_CM $CM* $CL;
191 ^$CM+ $CL; # by rule 10, stand-alone CM behaves as AL
223 $CanFollowIS = [$BK $CR $LF $NL $SP $ZW $WJ $GL $CL $CP $EX $IS $SY $QU $BA $HY $NS $ALPlus $HL $IN…
242 ($CL | $CP) $CM* $SP* $NS;
323 ($CM* ($CL | $CP))? ($CM* ($PR | $PO))?;
352 $RI $CM* $RI / [[^$BK $CR $LF $NL $SP $ZW $WJ $CL $CP $EX $IS $SY $GL $QU $BA $HY $…
353 $RI $CM* $RI $CM* [$CM-$ZWJ] / [[^$BK $CR $LF $NL $SP $ZW $WJ $CL $CP $EX $IS $SY $GL $QU $BA $HY $…
[all …]
|
| D | line.txt | 35 $CL = [:LineBreak = Close_Punctuation:];
118 $AL_FOLLOW = [$BK $CR $LF $NL $ZW $SP $CL $CP $EX $HL $IS $SY $WJ $GL $OP30 $QU $BA $HY $NS $I…
187 $LB8NonBreaks $CL;
188 $CAN_CM $CM* $CL;
189 ^$CM+ $CL; # by rule 10, stand-alone CM behaves as AL
221 $CanFollowIS = [$BK $CR $LF $NL $SP $ZW $WJ $GL $CL $CP $EX $IS $SY $QU $BA $HY $NS $ALPlus $HL $IN…
240 ($CL | $CP) $CM* $SP* $NS;
321 ($CM* ($CL | $CP))? ($CM* ($PR | $PO))?;
350 $RI $CM* $RI / [[^$BK $CR $LF $NL $SP $ZW $WJ $CL $CP $EX $IS $SY $GL $QU $BA $HY $…
351 $RI $CM* $RI $CM* [$CM-$ZWJ] / [[^$BK $CR $LF $NL $SP $ZW $WJ $CL $CP $EX $IS $SY $GL $QU $BA $HY $…
[all …]
|