/third_party/skia/third_party/externals/swiftshader/third_party/llvm-10.0/llvm/lib/ExecutionEngine/RuntimeDyld/ |
D | RTDyldMemoryManager.cpp | 163 #define ARM_MATH_IMPORTS(PP) \ argument 164 PP(__aeabi_d2f) \ 165 PP(__aeabi_d2iz) \ 166 PP(__aeabi_d2lz) \ 167 PP(__aeabi_d2uiz) \ 168 PP(__aeabi_d2ulz) \ 169 PP(__aeabi_dadd) \ 170 PP(__aeabi_dcmpeq) \ 171 PP(__aeabi_dcmpge) \ 172 PP(__aeabi_dcmpgt) \ [all …]
|
/third_party/boost/boost/safe_numerics/concept/ |
D | promotion_policy.hpp | 13 template<class PP> 17 using a_type = typename PP::template addition_result<T, U>; 18 using s_type = typename PP::template subtraction_result<T, U>; 19 using m_type = typename PP::template multiplication_result<T, U>; 20 using d_type = typename PP::template division_result<T, U>; 21 using mod_type = typename PP::template modulus_result<T, U>; 22 using ls_type = typename PP::template left_shift_result<T, U>; 23 using rs_type = typename PP::template right_shift_result<T, U>; 24 using cc_type = typename PP::template comparison_result<T, U>; 25 using baw_type = typename PP::template bitwise_and_result<T, U>; [all …]
|
/third_party/boost/libs/vmd/doc/ |
D | vmd_introduction.qbk | 14 to the functionality in the Boost preprocessor library ( Boost PP ), 17 In the Boost PP library the preprocessor data types which have 19 and the composite data types Boost PP arrays, Boost PP lists, 20 Boost PP seqs, and Boost PP tuples. 23 are the same data types as the Boost PP library as well as these other 32 of the Boost PP data types, but does extend some of that functionality 73 where the second Boost PP tuple element is empty. 77 In the Boost PP library a good deal of functionality centers upon 78 manipulating Boost PP numbers, and particularly the Boost PP numbers 79 of 0 and 1 as a boolean value on which you can use Boost PP [all …]
|
D | vmd_empty_ppdata.qbk | 10 Boost PP arrays and lists can be empty but seqs and tuples cannot. 18 small problem for Boost PP users. For a tuple, especially, not being 21 Boost PP preprocessor data. Otherwise, when using variadic macros, using 32 empty tuple; Boost PP functionality for a seq or tuple knows nothing about it. 33 In other words if you passed emptiness to a Boost PP macro which expects a 45 of macros which mimic many of those in Boost PP, but begin with BOOST_VMD_ 47 a 'VMD tuple', while the Boost PP equivalents work with the traditional seq 52 equivalent Boost PP functionality only accepts a normal seq or tuple. To be more 53 more precise the Boost PP functionality can accept a VMD seq or a VMD tuple as 55 non-empty VMD seq or a Boost PP seq, or between a non-empty VMD tuple and [all …]
|
D | vmd_naming.qbk | 14 in this library or Boost PP. These names and their data types are: 16 # TUPLE = Boost PP tuple data type. 17 # ARRAY = Boost PP array data type. 18 # LIST = Boost PP list data type. 19 # SEQ = Boost PP seq data type. 21 # NUMBER = A VMD number, which is a Boost PP number with some enhancements 24 I have used most of these names in order to mimic the naming of Boost PP 26 'seq', and 'tuple' refer to these Boost PP data types unless otherwise 27 noted. See the help for Boost PP for any explanation of these 31 same as a Boost PP sequence which is always referred to in this documentation
|
D | vmd_design.qbk | 11 working on another library of macro functionality, which used Boost PP 15 with Boost PP in the easiest and clearest way possible. 18 adding variadic macro data support to Boost PP. While this was being done, 19 but the variadic macro data support had not yet been finalized in Boost PP, 22 Boost PP library. 24 Once support for variadic data had been added to Boost PP I stripped 26 support for functionality which was an adjunct to the support in Boost PP. 28 which tested for empty input which Paul Mensonides, the author of Boost PP, had 35 I was able to build up some other macros which tested for the various Boost PP
|
D | vmd_variadic_macros.qbk | 19 found in Boost PP data types. 23 The Boost PP library has support for variadic macros and uses its 25 Boost PP defines or uses the macro BOOST_PP_VARIADICS to denote whether 29 If a user of Boost PP sets this value, Boost PP uses the value the end-user 30 sets, otherwise Boost PP defines the value of BOOST_PP_VARIADICS based on its 38 macro from Boost PP. The end-user of VMD can also manually
|
D | vmd_data_types.qbk | 37 VMD numbers are Boost PP numbers, ie. preprocessing tokens of 41 for which VMD offers specific functionality. The Boost PP library has it own extensive support 52 The Boost PP library supports four individual composite data types. These are arrays, 56 Boost PP is variadic data, which is a comma separated grouping of preprocessor elements. 57 VMD has no special support for variadic data outside of what is already in Boost PP. 59 VMD has functionality to work with the four Boost PP high-level data types. VMD can 60 test the Boost PP data types and parse them in a sequence of preprocessor tokens. 67 Emptiness, the three identifier types, the four Boost PP composite data types, and
|
/third_party/skia/gm/ |
D | mandoline.cpp | 72 SkPoint P[3] = {fLastPt, p1, p2}, PP[5]; in sliceQuadratic() local 73 SkChopQuadAt(P, PP, T); in sliceQuadratic() 74 this->sliceQuadratic(PP[1], PP[2], numSubdivisions - 1); in sliceQuadratic() 75 this->sliceQuadratic(PP[3], PP[4], numSubdivisions - 1); in sliceQuadratic() 92 SkPoint P[4] = {fLastPt, p1, p2, p3}, PP[7]; in sliceCubic() local 93 SkChopCubicAt(P, PP, T); in sliceCubic() 94 this->sliceCubic(PP[1], PP[2], PP[3], numSubdivisions - 1); in sliceCubic() 95 this->sliceCubic(PP[4], PP[5], PP[6], numSubdivisions - 1); in sliceCubic()
|
/third_party/flutter/skia/gm/ |
D | mandoline.cpp | 72 SkPoint P[3] = {fLastPt, p1, p2}, PP[5]; in sliceQuadratic() local 73 SkChopQuadAt(P, PP, T); in sliceQuadratic() 74 this->sliceQuadratic(PP[1], PP[2], numSubdivisions - 1); in sliceQuadratic() 75 this->sliceQuadratic(PP[3], PP[4], numSubdivisions - 1); in sliceQuadratic() 92 SkPoint P[4] = {fLastPt, p1, p2, p3}, PP[7]; in sliceCubic() local 93 SkChopCubicAt(P, PP, T); in sliceCubic() 94 this->sliceCubic(PP[1], PP[2], PP[3], numSubdivisions - 1); in sliceCubic() 95 this->sliceCubic(PP[4], PP[5], PP[6], numSubdivisions - 1); in sliceCubic()
|
/third_party/skia/third_party/externals/swiftshader/third_party/llvm-10.0/llvm/include/llvm/Analysis/ |
D | MustExecute.h | 402 iterator &begin(const Instruction *PP) { in begin() 403 auto *&It = InstructionIteratorMap[PP]; in begin() 405 It = new iterator(*this, PP); in begin() 410 const_iterator &begin(const Instruction *PP) const { in begin() 411 return *InstructionIteratorMap.lookup(PP); in begin() 424 llvm::iterator_range<iterator> range(const Instruction *PP) { in range() 425 return llvm::make_range(begin(PP), end(PP)); in range() 429 llvm::iterator_range<const_iterator> range(const Instruction *PP) const { in range() 430 return llvm::make_range(begin(PP), end(PP)); in range() 440 bool findInContextOf(const Instruction *I, const Instruction *PP) { in findInContextOf() [all …]
|
/third_party/flutter/skia/samplecode/ |
D | SampleCusp.cpp | 33 static SkPath cusp(const SkPoint P[4], SkPoint PP[7], bool& split, int speed, SkScalar phase) { in cusp() 45 SkChopCubicAt(P, PP, t); in cusp() 46 path.cubicTo(PP[1], PP[2], PP[3]); in cusp() 47 path.cubicTo(PP[4], PP[5], PP[6]); in cusp()
|
/third_party/skia/samplecode/ |
D | SampleCusp.cpp | 33 static SkPath cusp(const SkPoint P[4], SkPoint PP[7], bool& split, int speed, SkScalar phase) { in cusp() 45 SkChopCubicAt(P, PP, t); in cusp() 46 path.cubicTo(PP[1], PP[2], PP[3]); in cusp() 47 path.cubicTo(PP[4], PP[5], PP[6]); in cusp()
|
/third_party/iptables/extensions/ |
D | libxt_bpf.man | 6 .PP 12 .PP 19 .PP 25 .PP 38 .PP 42 .PP 46 .PP 57 .PP 59 .PP
|
D | libxt_osf.man | 29 .PP 31 .PP 34 .PP 37 .PP 39 .PP 41 .PP 43 .PP
|
D | libxt_rateest.man | 4 .PP 45 .PP 73 .PP 77 .PP 79 .PP 82 .PP 85 .PP 87 .PP 91 .PP 95 .PP
|
D | libxt_nfacct.man | 4 .PP 10 .PP 14 .PP 20 .PP 26 .PP
|
D | libxt_cpu.man | 6 .PP 8 .PP 11 .PP 14 .PP
|
D | libipt_REJECT.man | 33 .PP 37 .PP 44 .PP 46 .PP 48 .PP 50 .PP
|
D | libxt_SYNPROXY.man | 20 .PP 22 .PP 42 .PP 47 .PP 52 .PP 62 .PP
|
D | libip6t_REJECT.man | 33 .PP 37 .PP 44 .PP 46 .PP 48 .PP 50 .PP
|
D | libip6t_DNPT.man | 3 .PP 15 .PP 23 .PP 27 .PP
|
D | libip6t_SNPT.man | 3 .PP 15 .PP 23 .PP 27 .PP
|
/third_party/glslang/Test/ |
D | hlsl.pp.expand.frag | 9 float4 a EMP1({1,2,3,4}); // No PP arg errors 10 float4 b EMP2({({{(({1,2,3,4}))}})}, {{1,2,3,4}}); // No PP arg errors 11 float4 c EXP1({1,2,3,4}); // ERROR: No PP arg errors, but init error 12 float4 d EXP2({({{(({1,2,3,4}))}})}, {{1,2,3,4}}); // ERROR: No PP arg errors, but init error
|
/third_party/skia/third_party/externals/swiftshader/third_party/llvm-10.0/llvm/lib/Analysis/ |
D | MustExecute.cpp | 638 MustBeExecutedIterator &It, const Instruction *PP) { in getMustBeExecutedNextInstruction() argument 639 if (!PP) in getMustBeExecutedNextInstruction() 640 return PP; in getMustBeExecutedNextInstruction() 641 LLVM_DEBUG(dbgs() << "Find next instruction for " << *PP << "\n"); in getMustBeExecutedNextInstruction() 644 if (!ExploreInterBlock && PP->isTerminator()) { in getMustBeExecutedNextInstruction() 652 bool TransfersExecution = isGuaranteedToTransferExecutionToSuccessor(PP); in getMustBeExecutedNextInstruction() 660 if (!PP->isTerminator()) { in getMustBeExecutedNextInstruction() 661 const Instruction *NextPP = PP->getNextNode(); in getMustBeExecutedNextInstruction() 667 assert(PP->isTerminator() && "Expected a terminator!"); in getMustBeExecutedNextInstruction() 670 if (PP->getNumSuccessors() == 0) { in getMustBeExecutedNextInstruction() [all …]
|