| /external/clang/lib/CodeGen/ |
| D | CodeGenPGO.cpp | 206 CodeGenPGO &PGO; member
227 CodeGenPGO &PGO) in ComputeRegionCounts()
228 : PGO(PGO), RecordNextStmtCount(false), CountMap(CountMap) {} in ComputeRegionCounts()
252 uint64_t BodyCount = setCount(PGO.getRegionCount(D->getBody())); in VisitFunctionDecl()
264 uint64_t BodyCount = setCount(PGO.getRegionCount(D->getBody())); in VisitCapturedDecl()
271 uint64_t BodyCount = setCount(PGO.getRegionCount(D->getBody())); in VisitObjCMethodDecl()
278 uint64_t BodyCount = setCount(PGO.getRegionCount(D->getBody())); in VisitBlockDecl()
308 uint64_t BlockCount = setCount(PGO.getRegionCount(S)); in VisitLabelStmt()
336 uint64_t BodyCount = setCount(PGO.getRegionCount(S)); in VisitWhileStmt()
356 uint64_t LoopCount = PGO.getRegionCount(S); in VisitDoStmt()
[all …]
|
| /external/python/cpython2/PC/VS8.0/ |
| D | build_pgo.bat | 2 rem A batch program to build PGO (Profile guided optimization) by first
27 set PGO=%platf%-pgo variable
39 if exist %PGO% del /s /q %PGO%
|
| /external/python/cpython2/PC/VS9.0/ |
| D | build_pgo.bat | 2 rem A batch program to build PGO (Profile guided optimization) by first
27 set PGO=%platf%-pgo variable
39 if exist %PGO% del /s /q %PGO%
|
| D | readme.txt | 25 folders or profile guided optimization (PGO). The missing bits and pieces
44 land in the amd64 subfolder. The PGI and PGO builds for profile guided
207 The solution has two configurations for PGO. The PGInstrument
237 * pginstrument (PGO)
238 * pgupdate (PGO)
|
| /external/llvm/docs/ |
| D | AdvancedBuilds.rst | 80 Multi-stage PGO
83 Profile-Guided Optimizations (PGO) is a really great way to optimize the code
84 clang generates. Our multi-stage PGO builds are a workflow for generating PGO
87 At a high level, the way PGO works is that you build an instrumented compiler,
94 Our PGO.cmake cache script automates that whole process. You can use it by
99 $ cmake -G Ninja -C <path_to_clang>/cmake/caches/PGO.cmake <source dir>
119 The PGO came cache has a slightly different stage naming scheme than other
123 The PGO came cache generates the following additional targets:
135 compiler with the stage2 profdata to build a PGO-optimized compiler.
|
| /external/swiftshader/third_party/llvm-7.0/llvm/docs/ |
| D | AdvancedBuilds.rst | 80 Multi-stage PGO
83 Profile-Guided Optimizations (PGO) is a really great way to optimize the code
84 clang generates. Our multi-stage PGO builds are a workflow for generating PGO
87 At a high level, the way PGO works is that you build an instrumented compiler,
94 Our PGO.cmake cache script automates that whole process. You can use it by
99 $ cmake -G Ninja -C <path_to_clang>/cmake/caches/PGO.cmake <source dir>
119 The PGO came cache has a slightly different stage naming scheme than other
123 The PGO came cache generates the following additional targets:
135 compiler with the stage2 profdata to build a PGO-optimized compiler.
|
| /external/python/cpython3/Tools/msi/ |
| D | buildrelease.bat | 39 set PGO=-m test -q --pgo variable
61 if "%1" EQU "--pgo" (set PGO=%~2) && shift && shift && goto CheckOpts variable
62 if "%1" EQU "--skip-pgo" (set PGO=) && shift && goto CheckOpts variable
100 call :build x64 "%PGO%"
115 set PGO= variable
122 set PGO=%~2 variable
151 if not "%PGO%" EQU "" (
152 set PGOOPTS=--pgo-job "%PGO%"
219 echo --pgo Specify PGO command for x64 installers
220 echo --skip-pgo Build x64 installers without using PGO
|
| /external/clang/cmake/caches/ |
| D | README.txt | 28 PGO
31 The PGO CMake cache can be used to generate a multi-stage instrumented compiler.
34 cmake -G <generator> -C <path_to_clang>/cmake/caches/PGO.cmake <source dir>
48 compiler with the stage2 profdata to build a PGO-optimized compiler.
|
| D | PGO-stage2-instrumented.cmake | 8 -C ${CMAKE_CURRENT_LIST_DIR}/PGO-stage2.cmake
|
| D | PGO.cmake | 16 -C ${CMAKE_CURRENT_LIST_DIR}/PGO-stage2-instrumented.cmake
|
| /external/clang/utils/perf-training/ |
| D | CMakeLists.txt | 19 add_lit_testsuite(generate-profraw "Generating clang PGO data"
33 …message(FATAL_ERROR "Must set LLVM_PROFDATA to point to llvm-profdata to use for merging PGO data")
|
| D | README.txt | 6 generating PGO data and linker order files for clang.
|
| /external/python/cpython3/Lib/test/ |
| D | test_multiprocessing_spawn.py | 6 if support.PGO:
|
| D | test_multiprocessing_forkserver.py | 7 if support.PGO:
|
| D | test_multiprocessing_fork.py | 7 if support.PGO:
|
| /external/python/cpython3/Misc/NEWS.d/ |
| D | 3.7.2.rst | 17 It now adds profile-guided optimization (PGO) flags to ``CFLAGS_NODIST``:
|
| /external/python/cpython2/PCbuild/ |
| D | env.bat | 15 rem builds to find the PGO DLL. Do it first so the newer MSBuild is found
|
| D | build.bat | 46 echo. --pgo-job The job to use for PGO training; implies --pgo
92 echo.ERROR: Cannot cross-compile with PGO
|
| /external/llvm/docs/CommandGuide/ |
| D | llvm-profdata.rst | 37 generated by PGO instrumentation and merges them together into a single
107 optimization during PGO.
|
| /external/llvm/test/Bitcode/ |
| D | thinlto-function-summary-callgraph-pgo.ll | 1 ; Test to check the callgraph in summary when there is PGO
|
| /external/swiftshader/third_party/llvm-7.0/llvm/test/Instrumentation/InstrProfiling/ |
| D | PR23499.ll | 1 ;; Check that PGO instrumented variables associated with linkonce odr
|
| /external/python/cpython3/PCbuild/ |
| D | build.bat | 48 echo. --pgo-job The job to use for PGO training; implies --pgo
95 echo.ERROR: Cannot cross-compile with PGO
|
| /external/swiftshader/third_party/llvm-7.0/llvm/docs/CommandGuide/ |
| D | llvm-profdata.rst | 37 generated by PGO instrumentation and merges them together into a single
107 optimization during PGO.
|
| /external/autotest/test_suites/ |
| D | control.AFDO_record | 19 with traditional PGO.
|
| /external/swiftshader/third_party/llvm-7.0/llvm/test/Transforms/CodeGenPrepare/ |
| D | section.ll | 39 ; For instrumentation based PGO, we should only look at block counts,
|