| Name | Date | Size | #Lines | LOC | ||
|---|---|---|---|---|---|---|
| .. | - | - | ||||
| Inputs/ | 04-Jul-2025 | - | 504 | 432 | ||
| README | D | 04-Jul-2025 | 859 | 17 | 12 | |
| c-avoid-direct-call.c | D | 04-Jul-2025 | 365 | 12 | 5 | |
| c-captured.c | D | 04-Jul-2025 | 2.3 KiB | 60 | 18 | |
| c-counter-overflows.c | D | 04-Jul-2025 | 1.9 KiB | 50 | 19 | |
| c-general.c | D | 04-Jul-2025 | 19.5 KiB | 563 | 184 | |
| c-generate.c | D | 04-Jul-2025 | 947 | 16 | 3 | |
| c-indirect-call.c | D | 04-Jul-2025 | 681 | 17 | 5 | |
| c-linkage-available_externally.c | D | 04-Jul-2025 | 684 | 12 | 4 | |
| c-linkage.c | D | 04-Jul-2025 | 889 | 27 | 11 | |
| c-outdated-data.c | D | 04-Jul-2025 | 825 | 29 | 15 | |
| c-unprofiled-blocks.c | D | 04-Jul-2025 | 1.9 KiB | 70 | 31 | |
| c-unprofiled.c | D | 04-Jul-2025 | 1,005 | 27 | 12 | |
| c-unreachable-after-switch.c | D | 04-Jul-2025 | 540 | 16 | 6 | |
| cxx-class.cpp | D | 04-Jul-2025 | 2.9 KiB | 79 | 23 | |
| cxx-implicit.cpp | D | 04-Jul-2025 | 1.5 KiB | 52 | 27 | |
| cxx-indirect-call.cpp | D | 04-Jul-2025 | 723 | 22 | 7 | |
| cxx-lambda.cpp | D | 04-Jul-2025 | 2.3 KiB | 59 | 15 | |
| cxx-linkage.cpp | D | 04-Jul-2025 | 863 | 26 | 11 | |
| cxx-rangefor.cpp | D | 04-Jul-2025 | 1.6 KiB | 45 | 16 | |
| cxx-structors.cpp | D | 04-Jul-2025 | 687 | 33 | 15 | |
| cxx-templates.cpp | D | 04-Jul-2025 | 1.9 KiB | 43 | 8 | |
| cxx-throws.cpp | D | 04-Jul-2025 | 3.5 KiB | 94 | 28 | |
| cxx-virtual-destructor-calls.cpp | D | 04-Jul-2025 | 1.1 KiB | 38 | 11 | |
| def-assignop.cpp | D | 04-Jul-2025 | 1.2 KiB | 32 | 14 | |
| def-ctors.cpp | D | 04-Jul-2025 | 1.3 KiB | 37 | 16 | |
| def-dtors.cpp | D | 04-Jul-2025 | 1 KiB | 31 | 15 | |
| func-entry.c | D | 04-Jul-2025 | 574 | 20 | 7 | |
| gcc-flag-compatibility.c | D | 04-Jul-2025 | 2.2 KiB | 43 | 7 | |
| objc-general.m | D | 04-Jul-2025 | 2.5 KiB | 76 | 61 | |
| profile-does-not-exist.c | D | 04-Jul-2025 | 217 | 5 | 0 | |
| profile-summary.c | D | 04-Jul-2025 | 571 | 26 | 16 |
README
1These are tests for instrumentation based profiling. This specifically means 2the -fprofile-instr-generate and -fprofile-instr-use driver flags. 3 4Tests in this directory should usually test both: 5 6 - the generation of instrumentation (-fprofile-instr-generate), and 7 - the use of profile data from instrumented runs (-fprofile-instr-use). 8 9In order to test -fprofile-instr-use without actually running an instrumented 10program, .profdata files are checked into Inputs/. 11 12The input source files must include a main function such that building with 13-fprofile-instr-generate and running the resulting program generates the same 14.profdata file that is consumed by the tests for -fprofile-instr-use. Even 15tests that only check -fprofile-instr-use should include such a main function, 16so that profile data can be regenerated as the .profdata file format evolves. 17