From 5b07572df23fa385b468786e4a8847ec74d11795 Mon Sep 17 00:00:00 2001 From: Philip Reames Date: Sun, 26 Apr 2015 22:25:29 +0000 Subject: [PerformanceTips] Italics are *word*, not _word_ llvm-svn: 235827 --- llvm/docs/Frontend/PerformanceTips.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'llvm/docs/Frontend') diff --git a/llvm/docs/Frontend/PerformanceTips.rst b/llvm/docs/Frontend/PerformanceTips.rst index efc4d1c280f..22b3fe45984 100644 --- a/llvm/docs/Frontend/PerformanceTips.rst +++ b/llvm/docs/Frontend/PerformanceTips.rst @@ -142,18 +142,18 @@ Other things to consider this guidance is that a unified return block with high in-degree is fine. #. When checking a value against a constant, emit the check using a consistent - comparison type. The GVN pass _will_ optimize redundant equalities even if + comparison type. The GVN pass *will* optimize redundant equalities even if the type of comparison is inverted, but GVN only runs late in the pipeline. As a result, you may miss the opportunity to run other important optimizations. Improvements to EarlyCSE to remove this issue are tracked in Bug 23333. -#. Avoid using arithmetic intrinsics unless you are _required_ by your source +#. Avoid using arithmetic intrinsics unless you are *required* by your source language specification to emit a particular code sequence. The optimizer is quite good at reasoning about general control flow and arithmetic, it is not anywhere near as strong at reasoning about the various intrinsics. If profitable for code generation purposes, the optimizer will likely form the - intrinsics itself late in the optimization pipeline. It is _very_ rarely + intrinsics itself late in the optimization pipeline. It is *very* rarely profitable to emit these directly in the language frontend. This item explicitly includes the use of the :ref:`overflow intrinsics `. -- cgit v1.2.3