blob: 5c8ff2c0cf5d14f259387503bac1d4a366b50eae [file] [log] [blame]
Dmitri Gribenkoe17d8582012-12-09 23:14:26 +00001======================
Sean Silva4a535622013-01-20 03:29:50 +00002LLVM 3.3 Release Notes
Dmitri Gribenkoe17d8582012-12-09 23:14:26 +00003======================
4
5.. contents::
6 :local:
7
Sean Silva4a535622013-01-20 03:29:50 +00008.. warning::
9 These are in-progress notes for the upcoming LLVM 3.3 release. You may
10 prefer the `LLVM 3.2 Release Notes <http://llvm.org/releases/3.2/docs
11 /ReleaseNotes.html>`_.
Dmitri Gribenkoe17d8582012-12-09 23:14:26 +000012
Dmitri Gribenkoe17d8582012-12-09 23:14:26 +000013
14Introduction
15============
16
17This document contains the release notes for the LLVM Compiler Infrastructure,
Sean Silva4a535622013-01-20 03:29:50 +000018release 3.3. Here we describe the status of LLVM, including major improvements
Dmitri Gribenkoe17d8582012-12-09 23:14:26 +000019from the previous release, improvements in various subprojects of LLVM, and
20some of the current users of the code. All LLVM releases may be downloaded
21from the `LLVM releases web site <http://llvm.org/releases/>`_.
22
23For more information about LLVM, including information about the latest
24release, please check out the `main LLVM web site <http://llvm.org/>`_. If you
25have questions or comments, the `LLVM Developer's Mailing List
26<http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev>`_ is a good place to send
27them.
28
29Note that if you are reading this file from a Subversion checkout or the main
30LLVM web page, this document applies to the *next* release, not the current
31one. To see the release notes for a specific release, please see the `releases
32page <http://llvm.org/releases/>`_.
33
Sean Silva4a535622013-01-20 03:29:50 +000034Non-comprehensive list of changes in this release
35=================================================
Dmitri Gribenkoe17d8582012-12-09 23:14:26 +000036
Sean Silva4a535622013-01-20 03:29:50 +000037.. NOTE
38 For small 1-3 sentence descriptions, just add an entry at the end of
39 this list. If your description won't fit comfortably in one bullet
40 point (e.g. maybe you would like to give an example of the
41 functionality, or simply have a lot to talk about), see the `NOTE` below
42 for adding a new subsection.
Dmitri Gribenkoe17d8582012-12-09 23:14:26 +000043
Sean Silva4a535622013-01-20 03:29:50 +000044* The CellSPU port has been removed. It can still be found in older versions.
Dmitri Gribenkoe17d8582012-12-09 23:14:26 +000045
Sean Silva4a535622013-01-20 03:29:50 +000046* The IR-level extended linker APIs (for example, to link bitcode files out of
47 archives) have been removed. Any existing clients of these features should
48 move to using a linker with integrated LTO support.
Dmitri Gribenkoe17d8582012-12-09 23:14:26 +000049
Sean Silva8a72eff2013-01-20 03:32:55 +000050* LLVM and Clang's documentation has been migrated to the `Sphinx
51 <http://sphinx-doc.org/>`_ documentation generation system which uses
52 easy-to-write reStructuredText. See `llvm/docs/README.txt` for more
53 information.
54
Sean Silvaa79535c2013-02-07 05:56:46 +000055* TargetTransformInfo (TTI) is a new interface that can be used by IR-level
56 passes to obtain target-specific information, such as the costs of
57 instructions. Only "Lowering" passes such as LSR and the vectorizer are
58 allowed to use the TTI infrastructure.
Nadav Rotem87c61572013-02-07 05:42:31 +000059
Sean Silvaa79535c2013-02-07 05:56:46 +000060* We've improved the X86 and ARM cost model.
Nadav Rotem2119cf02013-02-07 05:44:58 +000061
Bill Wendling6eaab0d2013-02-13 21:10:15 +000062* The Attributes classes have been completely rewritten and expanded. They now
63 support not only enumerated attributes and alignments, but "string"
64 attributes, which are useful for passing information to code generation. See
Sean Silva3e1a7212013-02-26 18:22:18 +000065 :doc:`HowToUseAttributes` for more details.
Bill Wendling6eaab0d2013-02-13 21:10:15 +000066
Jakob Stoklund Olesena2310332013-03-25 00:36:53 +000067* TableGen's syntax for instruction selection patterns has been simplified.
68 Instead of specifying types indirectly with register classes, you should now
69 specify types directly in the input patterns. See ``SparcInstrInfo.td`` for
70 examples of the new syntax. The old syntax using register classes still
71 works, but it will be removed in a future LLVM release.
72
Sean Silva4a535622013-01-20 03:29:50 +000073* ... next change ...
Dmitri Gribenkoe17d8582012-12-09 23:14:26 +000074
Sean Silva4a535622013-01-20 03:29:50 +000075.. NOTE
76 If you would like to document a larger change, then you can add a
77 subsection about it right here. You can copy the following boilerplate
78 and un-indent it (the indentation causes it to be inside this comment).
Dmitri Gribenkoe17d8582012-12-09 23:14:26 +000079
Sean Silva4a535622013-01-20 03:29:50 +000080 Special New Feature
81 -------------------
Dmitri Gribenkoe17d8582012-12-09 23:14:26 +000082
Sean Silva4a535622013-01-20 03:29:50 +000083 Makes programs 10x faster by doing Special New Thing.
Dmitri Gribenkoe17d8582012-12-09 23:14:26 +000084
Tim Northover0f80f7b2013-02-13 12:46:32 +000085AArch64 target
86--------------
87
88We've added support for AArch64, ARM's 64-bit architecture. Development is still
89in fairly early stages, but we expect successful compilation when:
90
91- compiling standard compliant C99 and C++03 with Clang;
92- using Linux as a target platform;
93- where code + static data doesn't exceed 4GB in size (heap allocated data has
94 no limitation).
95
96Some additional functionality is also implemented, notably DWARF debugging,
97GNU-style thread local storage and inline assembly.
98
Matthew Curtis29da0432013-03-12 12:20:51 +000099Hexagon Target
100--------------
101
Matthew Curtis624ec292013-03-18 13:08:24 +0000102- Removed support for legacy hexagonv2 and hexagonv3 processor
103 architectures which are no longer in use. Currently supported
104 architectures are hexagonv4 and hexagonv5.
Matthew Curtis29da0432013-03-12 12:20:51 +0000105
Sean Silvaa79535c2013-02-07 05:56:46 +0000106Loop Vectorizer
107---------------
108
109We've continued the work on the loop vectorizer. The loop vectorizer now
110has the following features:
111
Nadav Rotem6f4888f2013-04-30 21:04:04 +0000112- Loops with unknown trip counts.
113- Runtime checks of pointers.
114- Reductions, Inductions.
115- Min/Max reductions of integers.
116- If Conversion.
117- Pointer induction variables.
118- Reverse iterators.
119- Vectorization of mixed types.
120- Vectorization of function calls.
121- Partial unrolling during vectorization.
Sean Silvaa79535c2013-02-07 05:56:46 +0000122
Nadav Rotem74cd12b2013-04-15 22:10:39 +0000123The loop vectorizer is now enabled by default for -O3.
124
125SLP Vectorizer
126--------------
127
128LLVM now has a new SLP vectorizer. The new SLP vectorizer is not enabled by
129default but can be enabled using the clang flag -fslp-vectorize. The BB-vectorizer
130can also be enabled using the command line flag -fslp-vectorize-aggressive.
131
Tom Stellard1c66a182013-02-08 22:24:41 +0000132R600 Backend
133------------
134
135The R600 backend was added in this release, it supports AMD GPUs
136(HD2XXX - HD7XXX). This backend is used in AMD's Open Source
137graphics / compute drivers which are developed as part of the `Mesa3D
138<http://www.mesa3d.org>`_ project.
139
Sean Silvaa79535c2013-02-07 05:56:46 +0000140
Pekka Jaaskelainen555e8f62013-05-03 07:37:04 +0000141External Open Source Projects Using LLVM 3.3
142============================================
143
144An exciting aspect of LLVM is that it is used as an enabling technology for
145a lot of other language and tools projects. This section lists some of the
146projects that have already been updated to work with LLVM 3.3.
147
148
149Portable Computing Language (pocl)
150----------------------------------
151
152In addition to producing an easily portable open source OpenCL
153implementation, another major goal of `pocl <http://pocl.sourceforge.net/>`_
154is improving performance portability of OpenCL programs with
155compiler optimizations, reducing the need for target-dependent manual
156optimizations. An important part of pocl is a set of LLVM passes used to
157statically parallelize multiple work-items with the kernel compiler, even in
158the presence of work-group barriers. This enables static parallelization of
159the fine-grained static concurrency in the work groups in multiple ways.
160
161TTA-based Co-design Environment (TCE)
162-------------------------------------
163
164`TCE <http://tce.cs.tut.fi/>`_ is a toolset for designing new
165processors based on the Transport triggered architecture (TTA).
166The toolset provides a complete co-design flow from C/C++
167programs down to synthesizable VHDL/Verilog and parallel program binaries.
168Processor customization points include the register files, function units,
169supported operations, and the interconnection network.
170
171TCE uses Clang and LLVM for C/C++/OpenCL C language support, target independent
172optimizations and also for parts of code generation. It generates new
173LLVM-based code generators "on the fly" for the designed TTA processors and
174loads them in to the compiler backend as runtime libraries to avoid
175per-target recompilation of larger parts of the compiler chain.
176
Sean Silvaa79535c2013-02-07 05:56:46 +0000177
Dmitri Gribenkoe17d8582012-12-09 23:14:26 +0000178Additional Information
179======================
180
181A wide variety of additional information is available on the `LLVM web page
182<http://llvm.org/>`_, in particular in the `documentation
183<http://llvm.org/docs/>`_ section. The web page also contains versions of the
184API documentation which is up-to-date with the Subversion version of the source
185code. You can access versions of these documents specific to this release by
186going into the ``llvm/docs/`` directory in the LLVM tree.
187
188If you have any questions or comments about LLVM, please feel free to contact
189us via the `mailing lists <http://llvm.org/docs/#maillist>`_.
190