Searched refs:TypeS (Results 1 – 25 of 27) sorted by relevance
12
| /external/clang/lib/AST/ |
| D | StmtPrinter.cpp | 2161 std::string TypeS; in VisitCXXNewExpr() local
2163 llvm::raw_string_ostream s(TypeS); in VisitCXXNewExpr()
2168 E->getAllocatedType().print(OS, Policy, TypeS); in VisitCXXNewExpr()
|
| /external/swiftshader/third_party/LLVM/docs/ |
| D | doxygen.cfg.in | 268 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
270 # namespace, or class. And the struct will be named TypeS. This can typically
|
| /external/antlr/runtime/C/ |
| D | doxyfile | 278 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
280 # namespace, or class. And the struct will be named TypeS. This can typically
|
| /external/mesa3d/src/gallium/state_trackers/clover/ |
| D | Doxyfile | 288 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
290 # namespace, or class. And the struct will be named TypeS. This can typically
|
| /external/eigen/doc/ |
| D | Doxyfile.in | 354 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
356 # namespace, or class. And the struct will be named TypeS. This can typically
|
| /external/libnl/doc/ |
| D | Doxyfile.in | 323 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
325 # namespace, or class. And the struct will be named TypeS. This can typically
|
| /external/libxkbcommon/xkbcommon/doc/ |
| D | Doxyfile.in | 326 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
328 # namespace, or class. And the struct will be named TypeS. This can typically
|
| /external/libxcam/doc/ |
| D | Doxyfile | 367 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
369 # namespace, or class. And the struct will be named TypeS. This can typically be
|
| /external/llvm/docs/ |
| D | doxygen.cfg.in | 367 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
369 # namespace, or class. And the struct will be named TypeS. This can typically be
|
| /external/clang/docs/ |
| D | doxygen.cfg.in | 367 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
369 # namespace, or class. And the struct will be named TypeS. This can typically be
|
| /external/swiftshader/third_party/llvm-7.0/llvm/docs/ |
| D | doxygen.cfg.in | 368 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
370 # namespace, or class. And the struct will be named TypeS. This can typically be
|
| /external/flatbuffers/docs/source/ |
| D | doxyfile | 377 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
379 # namespace, or class. And the struct will be named TypeS. This can typically be
|
| /external/swiftshader/third_party/subzero/docs/ |
| D | Doxyfile | 367 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
369 # namespace, or class. And the struct will be named TypeS. This can typically be
|
| /external/jsoncpp/doc/ |
| D | doxyfile.in | 378 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
380 # namespace, or class. And the struct will be named TypeS. This can typically be
|
| /external/grpc-grpc/templates/tools/doxygen/ |
| D | Doxyfile.include | 406 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
408 # namespace, or class. And the struct will be named TypeS. This can typically be
|
| /external/Reactive-Extensions/RxCpp/projects/doxygen/ |
| D | doxygen.conf.in | 390 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
392 # namespace, or class. And the struct will be named TypeS. This can typically be
|
| /external/ImageMagick/config/ |
| D | Magick++.dox.in | 394 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
396 # namespace, or class. And the struct will be named TypeS. This can typically be
|
| D | MagickWand.dox.in | 394 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
396 # namespace, or class. And the struct will be named TypeS. This can typically be
|
| D | MagickCore.dox.in | 394 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
396 # namespace, or class. And the struct will be named TypeS. This can typically be
|
| /external/libusb/doc/ |
| D | doxygen.cfg.in | 378 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
380 # namespace, or class. And the struct will be named TypeS. This can typically be
|
| /external/tinyxml2/ |
| D | dox | 398 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
400 # namespace, or class. And the struct will be named TypeS. This can typically be
|
| /external/parameter-framework/upstream/doc/ |
| D | Doxyfile.in | 378 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
380 # namespace, or class. And the struct will be named TypeS. This can typically be
|
| /external/skia/tools/doxygen/ |
| D | Doxyfile | 404 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
406 # namespace, or class. And the struct will be named TypeS. This can typically be
|
| /external/grpc-grpc/tools/doxygen/ |
| D | Doxyfile.core | 380 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
382 # namespace, or class. And the struct will be named TypeS. This can typically be
|
| /external/icu/icu4c/source/ |
| D | Doxyfile.in | 408 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
410 # namespace, or class. And the struct will be named TypeS. This can typically be
|
12