forked from OSchip/llvm-project
52faad83c9
When this pass was originally implemented, the fix pass was enabled using a llvm command-line flag. This works fine, except in the case of LTO, where the flag is not passed into the linker plugin in order to enable the function pass in the LTO backend. Now LTO exists, the expectation now is to use target features rather than command-line arguments to control code generation, as this ensures that different command-line arguments in different files are correctly represented, and target-features always get to the LTO plugin as they are encoded into LLVM IR. The fall-out of this change is that the fix pass has to always be added to the backend pass pipeline, so now it makes no changes if the function does not have the right target feature to enable it. This should make a minimal difference to compile time. One advantage is it's now much easier to enable when compiling for a Cortex-A53, as CPUs imply their own individual sets of target-features, in a more fine-grained way. I haven't done this yet, but it is an option, if the fix should be enabled in more places. Existing tests of the user interface are unaffected, the changes are to reflect that the argument is now turned into a target feature. Reviewed By: tmatheson Differential Revision: https://reviews.llvm.org/D114703 |
||
|---|---|---|
| .. | ||
| INPUTS | ||
| bindings | ||
| cmake | ||
| docs | ||
| examples | ||
| include | ||
| lib | ||
| runtime | ||
| test | ||
| tools | ||
| unittests | ||
| utils | ||
| www | ||
| .clang-format | ||
| .clang-tidy | ||
| .gitignore | ||
| CMakeLists.txt | ||
| CODE_OWNERS.TXT | ||
| INSTALL.txt | ||
| LICENSE.TXT | ||
| ModuleInfo.txt | ||
| NOTES.txt | ||
| README.txt | ||
README.txt
//===----------------------------------------------------------------------===// // C Language Family Front-end //===----------------------------------------------------------------------===// Welcome to Clang. This is a compiler front-end for the C family of languages (C, C++, Objective-C, and Objective-C++) which is built as part of the LLVM compiler infrastructure project. Unlike many other compiler frontends, Clang is useful for a number of things beyond just compiling code: we intend for Clang to be host to a number of different source-level tools. One example of this is the Clang Static Analyzer. If you're interested in more (including how to build Clang) it is best to read the relevant web sites. Here are some pointers: Information on Clang: http://clang.llvm.org/ Building and using Clang: http://clang.llvm.org/get_started.html Clang Static Analyzer: http://clang-analyzer.llvm.org/ Information on the LLVM project: http://llvm.org/ If you have questions or comments about Clang, a great place to discuss them is on the Clang development mailing list: http://lists.llvm.org/mailman/listinfo/cfe-dev If you find a bug in Clang, please file it in the LLVM bug tracker: http://llvm.org/bugs/