commit: 815f533bcd07ca6bf087a3f8e41c51b44c3e1a5b
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sun Nov 12 09:00:59 2017 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sun Nov 12 09:27:01 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=815f533b
sys-devel/llvm: Unify metadata.xml indentation
sys-devel/llvm/metadata.xml | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/sys-devel/llvm/metadata.xml b/sys-devel/llvm/metadata.xml
index 681eb777690..f532f3a746d 100644
--- a/sys-devel/llvm/metadata.xml
+++ b/sys-devel/llvm/metadata.xml
@@ -5,10 +5,10 @@
<email>[email protected]</email>
</maintainer>
<longdescription>Low Level Virtual Machine (LLVM) is:
- 1. A compilation strategy designed to enable effective program optimization
across the entire lifetime of a program. LLVM supports effective optimization
at compile time, link-time (particularly interprocedural), run-time and offline
(i.e., after software is installed), while remaining transparent to developers
and maintaining compatibility with existing build scripts.
- 2. A virtual instruction set - LLVM is a low-level object code
representation that uses simple RISC-like instructions, but provides rich,
language-independent, type information and dataflow (SSA) information about
operands. This combination enables sophisticated transformations on object
code, while remaining light-weight enough to be attached to the executable.
This combination is key to allowing link-time, run-time, and offline
transformations.
- 3. A compiler infrastructure - LLVM is also a collection of source code
that implements the language and compilation strategy. The primary components
of the LLVM infrastructure are a GCC-based C and C++ front-end, a link-time
optimization framework with a growing set of global and interprocedural
analyses and transformations, static back-ends for many popular (and some
obscure) architectures, a back-end which emits portable C code, and a
Just-In-Time compilers for several architectures.
- 4. LLVM does not imply things that you would expect from a high-level
virtual machine. It does not require garbage collection or run-time code
generation (In fact, LLVM makes a great static compiler!). Note that optional
LLVM components can be used to build high-level virtual machines and other
systems that need these services.</longdescription>
+ 1. A compilation strategy designed to enable effective program
optimization across the entire lifetime of a program. LLVM supports effective
optimization at compile time, link-time (particularly interprocedural),
run-time and offline (i.e., after software is installed), while remaining
transparent to developers and maintaining compatibility with existing build
scripts.
+ 2. A virtual instruction set - LLVM is a low-level object code
representation that uses simple RISC-like instructions, but provides rich,
language-independent, type information and dataflow (SSA) information about
operands. This combination enables sophisticated transformations on object
code, while remaining light-weight enough to be attached to the executable.
This combination is key to allowing link-time, run-time, and offline
transformations.
+ 3. A compiler infrastructure - LLVM is also a collection of source code
that implements the language and compilation strategy. The primary components
of the LLVM infrastructure are a GCC-based C and C++ front-end, a link-time
optimization framework with a growing set of global and interprocedural
analyses and transformations, static back-ends for many popular (and some
obscure) architectures, a back-end which emits portable C code, and a
Just-In-Time compilers for several architectures.
+ 4. LLVM does not imply things that you would expect from a high-level
virtual machine. It does not require garbage collection or run-time code
generation (In fact, LLVM makes a great static compiler!). Note that optional
LLVM components can be used to build high-level virtual machines and other
systems that need these services.</longdescription>
<use>
<flag name="clang">Build the clang C/C++ compiler</flag>
<flag name="default-compiler-rt">Use compiler-rt instead of
libgcc as the default rtlib for clang</flag>
