From da585f0830d2db0577b2be6a40a3c31041741ba0 Mon Sep 17 00:00:00 2001 From: Francesco Petrogalli Date: Thu, 19 Sep 2019 14:19:32 +0000 Subject: [PATCH] [docs] Break long (>80) line. NFC git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@372326 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/Frontend/PerformanceTips.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/Frontend/PerformanceTips.rst b/docs/Frontend/PerformanceTips.rst index 142d262eb65..2c356de14cd 100644 --- a/docs/Frontend/PerformanceTips.rst +++ b/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 -- 2.50.1