| /third_party/typescript/src/compiler/ |
| D | moduleNameResolver.ts | 14 …(packageInfo: PackageJsonInfo | undefined, r: PathAndExtension | undefined): Resolved | undefined {
29 function noPackageId(r: PathAndExtension | undefined): Resolved | undefined {
33 function removeIgnoredPackageId(r: Resolved | undefined): PathAndExtension | undefined {
41 interface Resolved { interface
80 function resolvedTypeScriptOnly(resolved: Resolved | undefined): PathAndPackageId | undefined {
88 …function createResolvedModuleWithFailedLookupLocations(resolved: Resolved | undefined, isExternalL…
378 let result: Resolved | undefined;
728 …didate: string, onlyRecordFailures: boolean, state: ModuleResolutionState) => Resolved | undefined;
791 state: ModuleResolutionState): Resolved | undefined {
819 state: ModuleResolutionState): Resolved | undefined {
[all …]
|
| /third_party/skia/third_party/externals/swiftshader/third_party/llvm-10.0/llvm/lib/ExecutionEngine/Orc/ |
| D | RTDyldObjectLinkingLayer.cpp | 54 SymbolState::Resolved, std::move(OnResolvedWithUnwrap), in lookup()
160 std::map<StringRef, JITEvaluatedSymbol> Resolved, in onObjLoad() argument
179 auto I = Resolved.find(*Name); in onObjLoad()
183 if (I == Resolved.end() || InternalSymbols.count(*Name) || in onObjLoad()
197 for (auto &KV : Resolved) { in onObjLoad()
|
| /third_party/skia/third_party/externals/swiftshader/third_party/llvm-10.0/llvm/lib/Analysis/ |
| D | BlockFrequencyInfoImpl.cpp | 302 BlockNode Resolved = Working[Succ.Index].getResolvedNode(); in addToDist() local
308 if (!isLoopHeader(Resolved)) in addToDist()
310 if (Resolved != Succ) in addToDist()
311 dbgs() << ", resolved = " << getBlockName(Resolved); in addToDist()
317 if (isLoopHeader(Resolved)) { in addToDist()
319 Dist.addBackedge(Resolved, Weight); in addToDist()
323 if (Working[Resolved.Index].getContainingLoop() != OuterLoop) { in addToDist()
325 Dist.addExit(Resolved, Weight); in addToDist()
329 if (Resolved < Pred) { in addToDist()
343 assert(OuterLoop && OuterLoop->isIrreducible() && !isLoopHeader(Resolved) && in addToDist()
[all …]
|
| /third_party/vk-gl-cts/external/vulkan-docs/src/appendices/ |
| D | VK_EXT_opacity_micromap.adoc | 116 * Resolved: The build should be much lighter-weight than an acceleration
123 * Resolved: There can be a very large number of these structures, so
133 * Resolved: There is a ray flag.
140 * Resolved: Not for now.
148 * Resolved: There is no need right now (can just use the handle) but that
156 * Resolved: This is most parallel with the definition of
|
| /third_party/openGLES/extensions/EXT/ |
| D | EXT_framebuffer_blit.txt | 501 Resolved: use explicit rects, so we don't need to perform
506 Resolved: use (start,end). This is a break from the past
512 Resolved: BlitFramebufferEXT
516 Resolved: No
521 Resolved: Generate ERROR_INVALID_OPERATION
526 Resolved: Generate ERROR_INVALID_OPERATION
531 Resolved: concensus leans toward separate Read/Draw entry
538 Resolved: Yes. Binding to the legacy target FRAMEBUFFER sets
549 Resolved: always return the value associated with the
555 Resolved: Accum returns INVALID_OPERATION if the
[all …]
|
| D | EXT_draw_instanced.txt | 187 Resolved: While this extension could stand alone, its utility
199 Resolved: No, this may cause implementation difficulties and
205 Resolved: No, calling these during display list compilation
211 Resolved: According to the The OpenGL ES Shading Language
|
| D | EXT_debug_label.txt | 301 Resolved: No.
312 Resolved: No.
323 Resolved: No.
332 Resolved: No, since some objects require more information (e.g. a texture
|
| /third_party/skia/third_party/externals/opengl-registry/extensions/EXT/ |
| D | EXT_framebuffer_blit.txt | 501 Resolved: use explicit rects, so we don't need to perform
506 Resolved: use (start,end). This is a break from the past
512 Resolved: BlitFramebufferEXT
516 Resolved: No
521 Resolved: Generate ERROR_INVALID_OPERATION
526 Resolved: Generate ERROR_INVALID_OPERATION
531 Resolved: concensus leans toward separate Read/Draw entry
538 Resolved: Yes. Binding to the legacy target FRAMEBUFFER sets
549 Resolved: always return the value associated with the
555 Resolved: Accum returns INVALID_OPERATION if the
[all …]
|
| D | EXT_draw_instanced.txt | 187 Resolved: While this extension could stand alone, its utility
199 Resolved: No, this may cause implementation difficulties and
205 Resolved: No, calling these during display list compilation
211 Resolved: According to the The OpenGL ES Shading Language
|
| D | EXT_debug_label.txt | 301 Resolved: No.
312 Resolved: No.
323 Resolved: No.
332 Resolved: No, since some objects require more information (e.g. a texture
|
| /third_party/skia/third_party/externals/opengl-registry/extensions/ARB/ |
| D | ARB_shader_bit_encoding.txt | 98 Resolved. Currently ARB_shader_bit_encoding.
103 Resolved. Given the deadline, hearing no additional candidates for
108 Resolved. Certainly. They will be found in ARB_gpu_shader5. This
|
| D | ARB_shader_atomic_counters.txt | 952 Resolved. All stages.
956 Resolved: Not directly. But indirectly, probably not in
962 Resolved. It's here.
967 Resolved: Yes, with caveats. In order to provide a global unique
980 Resolved. Yes, with the same caveats as above.
984 Resolved. No, implementations are free to support arbitrarily many
990 Resolved: Yes. (It's an increment of zero. Or a decrement of zero.)
998 Resolved: No. Only by 1. (Or 0.)
1002 Resolved: Wrap. [0,2^32-1]
1006 Resolved: There is no context state, they must be backed
[all …]
|
| /third_party/skia/third_party/externals/swiftshader/third_party/llvm-10.0/llvm/lib/MC/ |
| D | MCAsmBackend.cpp | 107 const MCFixup &Fixup, bool Resolved, uint64_t Value, in fixupNeedsRelaxationAdvanced() argument
110 if (!Resolved) in fixupNeedsRelaxationAdvanced()
|
| /third_party/openGLES/extensions/ARB/ |
| D | ARB_shader_atomic_counters.txt | 962 Resolved. All stages.
966 Resolved: Not directly. But indirectly, probably not in
972 Resolved. It's here.
977 Resolved: Yes, with caveats. In order to provide a global unique
990 Resolved. Yes, with the same caveats as above.
994 Resolved. No, implementations are free to support arbitrarily many
1000 Resolved: Yes. (It's an increment of zero. Or a decrement of zero.)
1008 Resolved: No. Only by 1. (Or 0.)
1012 Resolved: Wrap. [0,2^32-1]
1016 Resolved: There is no context state, they must be backed
[all …]
|
| D | ARB_shader_bit_encoding.txt | 108 Resolved. Currently ARB_shader_bit_encoding.
113 Resolved. Given the deadline, hearing no additional candidates for
118 Resolved. Certainly. They will be found in ARB_gpu_shader5. This
|
| /third_party/skia/third_party/externals/opengl-registry/extensions/NV/ |
| D | NV_copy_image.txt | 285 Resolved.
295 Resolved.
302 Resolved.
310 Resolved.
321 Resolved.
329 Resolved.
340 Resolved.
352 Resolved.
|
| /third_party/openGLES/extensions/NV/ |
| D | NV_copy_image.txt | 285 Resolved.
295 Resolved.
302 Resolved.
310 Resolved.
321 Resolved.
329 Resolved.
340 Resolved.
352 Resolved.
|
| /third_party/skia/third_party/externals/opengl-registry/extensions/OVR/ |
| D | OVR_multiview.txt | 462 Resolved: Not in this extension. By disallowing it, we hope to enable more
468 Resolved: No, while there might be some uses for such support, it adds
475 Resolved: GS could be used to achieve stereo rendering by broadcasting each
483 Resolved: Use of arrays does imply that we use a minimum version of GL and
493 Resolved: The bias will be toward relaxed rules to allow implementation
500 Resolved: To make integration simple for app developers, the intent is for
505 Resolved: No. This is implicit in the dependence of a parameter on ViewID.
514 Resolved: No. Letting the app index via ViewID makes it a lot harder for the
522 Resolved: No. Exposing the gl_ViewID_OVR variable is the smallest change. It
531 Resolved: Almost certainly in GL 4.5 and beyond. Less clear that it should
[all …]
|
| /third_party/openGLES/extensions/OVR/ |
| D | OVR_multiview.txt | 472 Resolved: Not in this extension. By disallowing it, we hope to enable more
478 Resolved: No, while there might be some uses for such support, it adds
485 Resolved: GS could be used to achieve stereo rendering by broadcasting each
493 Resolved: Use of arrays does imply that we use a minimum version of GL and
503 Resolved: The bias will be toward relaxed rules to allow implementation
510 Resolved: To make integration simple for app developers, the intent is for
515 Resolved: No. This is implicit in the dependence of a parameter on ViewID.
524 Resolved: No. Letting the app index via ViewID makes it a lot harder for the
532 Resolved: No. Exposing the gl_ViewID_OVR variable is the smallest change. It
541 Resolved: Almost certainly in GL 4.5 and beyond. Less clear that it should
[all …]
|
| /third_party/skia/modules/skparagraph/src/ |
| D | OneLineShaper.h | 63 enum Resolved { enum
69 using TypefaceVisitor = std::function<Resolved(sk_sp<SkTypeface> typeface)>;
|
| D | OneLineShaper.cpp | 483 if (visitor(typeface) == Resolved::Everything) { in matchResolvedFonts()
521 if (resolved == Resolved::Everything) { in matchResolvedFonts()
526 if (resolved == Resolved::Something) { in matchResolvedFonts()
704 return Resolved::Everything; in shape()
706 return Resolved::Something; in shape()
708 return Resolved::Nothing; in shape()
|
| /third_party/openGLES/extensions/AMD/ |
| D | WGL_AMD_gpu_association.txt | 434 - Resolved. It seems unnecessary. An associated DC would be a virtual
441 - Resolved. There is no need to create a restriction. The GPU info can
447 - Resolved. It is the applications responsibility to use each GPU
454 - Resolved. It seems feasible to have an associated context and a normal
462 -Resolved. This is not an issue.
467 - Resolved. This is sufficent. One alternative would be to test execution of
475 - Resolved. Both methods would work well. Adding a new function prevents
484 - Resolved. Using the pixel format would provide a non-intrusive solution,
492 - Resolved. This is not an issue.
|
| /third_party/skia/third_party/externals/opengl-registry/extensions/AMD/ |
| D | WGL_AMD_gpu_association.txt | 434 - Resolved. It seems unnecessary. An associated DC would be a virtual
441 - Resolved. There is no need to create a restriction. The GPU info can
447 - Resolved. It is the applications responsibility to use each GPU
454 - Resolved. It seems feasible to have an associated context and a normal
462 -Resolved. This is not an issue.
467 - Resolved. This is sufficent. One alternative would be to test execution of
475 - Resolved. Both methods would work well. Adding a new function prevents
484 - Resolved. Using the pixel format would provide a non-intrusive solution,
492 - Resolved. This is not an issue.
|
| /third_party/json/third_party/amalgamate/ |
| D | CHANGES.md | 3 - Resolved inspection results from PyCharm:
|
| /third_party/mesa3d/docs/_extra/specs/ |
| D | MESA_pack_invert.spec | 53 Resolved: No, we're only concerned with pixel packing. There are other
|