summaryrefslogtreecommitdiffstats
path: root/llvm/docs/Frontend
diff options
context:
space:
mode:
authorFrancesco Petrogalli <francesco.petrogalli@arm.com>2019-09-19 14:19:32 +0000
committerFrancesco Petrogalli <francesco.petrogalli@arm.com>2019-09-19 14:19:32 +0000
commitcde4f727fffe4ea04ae95f831ba788781d2f20eb (patch)
treec813d1bf98fe4ff1912526d1da534d890daa7310 /llvm/docs/Frontend
parented9104c3f8781ed6f5dc6e7d7034158d062c2510 (diff)
downloadbcm5719-llvm-cde4f727fffe4ea04ae95f831ba788781d2f20eb.tar.gz
bcm5719-llvm-cde4f727fffe4ea04ae95f831ba788781d2f20eb.zip
[docs] Break long (>80) line. NFC
llvm-svn: 372326
Diffstat (limited to 'llvm/docs/Frontend')
-rw-r--r--llvm/docs/Frontend/PerformanceTips.rst3
1 files changed, 2 insertions, 1 deletions
diff --git a/llvm/docs/Frontend/PerformanceTips.rst b/llvm/docs/Frontend/PerformanceTips.rst
index 142d262eb65..2c356de14cd 100644
--- a/llvm/docs/Frontend/PerformanceTips.rst
+++ b/llvm/docs/Frontend/PerformanceTips.rst
@@ -21,7 +21,8 @@ surprisingly small changes in the source IR can have a large effect on the
generated code.
Beyond the specific items on the list below, it's worth noting that the most
-mature frontend for LLVM is Clang. As a result, the further your IR gets from what Clang might emit, the less likely it is to be effectively optimized. It
+mature frontend for LLVM is Clang. As a result, the further your IR gets from
+what Clang might emit, the less likely it is to be effectively optimized. It
can often be useful to write a quick C program with the semantics you're trying
to model and see what decisions Clang's IRGen makes about what IR to emit.
Studying Clang's CodeGen directory can also be a good source of ideas. Note
OpenPOWER on IntegriCloud