forked from OSchip/llvm-project
93786da2cb
Much to my surprise, '-disable-llvm-optzns' which I thought was the magical flag I wanted to get at the raw LLVM IR coming out of Clang deosn't do that. It still runs some passes over the IR. I don't want that, I really want the *raw* IR coming out of Clang and I strongly suspect everyone else using it is in the same camp. There is actually a flag that does what I want that I didn't know about called '-disable-llvm-passes'. I suspect many others don't know about it either. It both does what I want and is much simpler. This removes the confusing version and makes that spelling of the flag an alias for '-disable-llvm-passes'. I've also moved everything in Clang to use the 'passes' spelling as it seems both more accurate (*all* LLVM passes are disabled, not just optimizations) and much easier to remember and spell correctly. This is part of simplifying how Clang drives LLVM to make it cleaner to wire up to the new pass manager. Differential Revision: https://reviews.llvm.org/D28047 llvm-svn: 290392 |
||
|---|---|---|
| .. | ||
| Inputs | ||
| README | ||
| c-avoid-direct-call.c | ||
| c-captured.c | ||
| c-counter-overflows.c | ||
| c-general.c | ||
| c-generate.c | ||
| c-indirect-call.c | ||
| c-linkage-available_externally.c | ||
| c-linkage.c | ||
| c-outdated-data.c | ||
| c-unprofiled-blocks.c | ||
| c-unprofiled.c | ||
| c-unreachable-after-switch.c | ||
| cxx-class.cpp | ||
| cxx-implicit.cpp | ||
| cxx-indirect-call.cpp | ||
| cxx-lambda.cpp | ||
| cxx-linkage.cpp | ||
| cxx-rangefor.cpp | ||
| cxx-stmt-initializers.cpp | ||
| cxx-structors.cpp | ||
| cxx-templates.cpp | ||
| cxx-throws.cpp | ||
| cxx-virtual-destructor-calls.cpp | ||
| def-assignop.cpp | ||
| def-ctors.cpp | ||
| def-dtors.cpp | ||
| func-entry.c | ||
| gcc-flag-compatibility.c | ||
| objc-general.m | ||
| profile-does-not-exist.c | ||
| profile-summary.c | ||
README
These are tests for instrumentation based profiling. This specifically means the -fprofile-instr-generate and -fprofile-instr-use driver flags. Tests in this directory should usually test both: - the generation of instrumentation (-fprofile-instr-generate), and - the use of profile data from instrumented runs (-fprofile-instr-use). In order to test -fprofile-instr-use without actually running an instrumented program, .profdata files are checked into Inputs/. The input source files must include a main function such that building with -fprofile-instr-generate and running the resulting program generates the same .profdata file that is consumed by the tests for -fprofile-instr-use. Even tests that only check -fprofile-instr-use should include such a main function, so that profile data can be regenerated as the .profdata file format evolves.