blob: 3689af18093f98da711f4354d569dcc1b7cd79d9 [file] [log] [blame]
Dmitri Gribenko38782b82012-12-09 23:14:26 +00001======================
Sean Silva1eab30d2013-01-20 03:29:50 +00002LLVM 3.3 Release Notes
Dmitri Gribenko38782b82012-12-09 23:14:26 +00003======================
4
5.. contents::
6 :local:
7
Sean Silva1eab30d2013-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 Gribenko38782b82012-12-09 23:14:26 +000012
Dmitri Gribenko38782b82012-12-09 23:14:26 +000013
14Introduction
15============
16
17This document contains the release notes for the LLVM Compiler Infrastructure,
Sean Silva1eab30d2013-01-20 03:29:50 +000018release 3.3. Here we describe the status of LLVM, including major improvements
Dmitri Gribenko38782b82012-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 Silva1eab30d2013-01-20 03:29:50 +000034Non-comprehensive list of changes in this release
35=================================================
Dmitri Gribenko38782b82012-12-09 23:14:26 +000036
Sean Silva1eab30d2013-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 Gribenko38782b82012-12-09 23:14:26 +000043
Sean Silva1eab30d2013-01-20 03:29:50 +000044* The CellSPU port has been removed. It can still be found in older versions.
Dmitri Gribenko38782b82012-12-09 23:14:26 +000045
Sean Silva1eab30d2013-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 Gribenko38782b82012-12-09 23:14:26 +000049
Sean Silvacc0614e2013-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 Silva5672a372013-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 Roteme56b0582013-02-07 05:42:31 +000059
Sean Silva5672a372013-02-07 05:56:46 +000060* We've improved the X86 and ARM cost model.
Nadav Rotemd58a6142013-02-07 05:44:58 +000061
Bill Wendlinga361c9d2013-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 Silvacf6848f2013-02-26 18:22:18 +000065 :doc:`HowToUseAttributes` for more details.
Bill Wendlinga361c9d2013-02-13 21:10:15 +000066
Jakob Stoklund Olesen8ef24192013-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
Rafael Espindolac2565852013-05-07 12:29:17 +000073* MCJIT now supports exception handling. Support for it in the old jit will be
74 removed in the 3.4 release.
75
Sean Silva1eab30d2013-01-20 03:29:50 +000076* ... next change ...
Dmitri Gribenko38782b82012-12-09 23:14:26 +000077
Sean Silva1eab30d2013-01-20 03:29:50 +000078.. NOTE
79 If you would like to document a larger change, then you can add a
80 subsection about it right here. You can copy the following boilerplate
81 and un-indent it (the indentation causes it to be inside this comment).
Dmitri Gribenko38782b82012-12-09 23:14:26 +000082
Sean Silva1eab30d2013-01-20 03:29:50 +000083 Special New Feature
84 -------------------
Dmitri Gribenko38782b82012-12-09 23:14:26 +000085
Sean Silva1eab30d2013-01-20 03:29:50 +000086 Makes programs 10x faster by doing Special New Thing.
Dmitri Gribenko38782b82012-12-09 23:14:26 +000087
Tim Northoverfb6f08d2013-02-13 12:46:32 +000088AArch64 target
89--------------
90
91We've added support for AArch64, ARM's 64-bit architecture. Development is still
92in fairly early stages, but we expect successful compilation when:
93
94- compiling standard compliant C99 and C++03 with Clang;
95- using Linux as a target platform;
96- where code + static data doesn't exceed 4GB in size (heap allocated data has
97 no limitation).
98
99Some additional functionality is also implemented, notably DWARF debugging,
100GNU-style thread local storage and inline assembly.
101
Matthew Curtise2228a72013-03-12 12:20:51 +0000102Hexagon Target
103--------------
104
Matthew Curtisa8b88cc2013-03-18 13:08:24 +0000105- Removed support for legacy hexagonv2 and hexagonv3 processor
106 architectures which are no longer in use. Currently supported
107 architectures are hexagonv4 and hexagonv5.
Matthew Curtise2228a72013-03-12 12:20:51 +0000108
Sean Silva5672a372013-02-07 05:56:46 +0000109Loop Vectorizer
110---------------
111
112We've continued the work on the loop vectorizer. The loop vectorizer now
113has the following features:
114
Nadav Rotem4b01c3a2013-04-30 21:04:04 +0000115- Loops with unknown trip counts.
116- Runtime checks of pointers.
117- Reductions, Inductions.
118- Min/Max reductions of integers.
119- If Conversion.
120- Pointer induction variables.
121- Reverse iterators.
122- Vectorization of mixed types.
123- Vectorization of function calls.
124- Partial unrolling during vectorization.
Sean Silva5672a372013-02-07 05:56:46 +0000125
Nadav Rotem2ee204d2013-04-15 22:10:39 +0000126The loop vectorizer is now enabled by default for -O3.
127
128SLP Vectorizer
129--------------
130
131LLVM now has a new SLP vectorizer. The new SLP vectorizer is not enabled by
132default but can be enabled using the clang flag -fslp-vectorize. The BB-vectorizer
133can also be enabled using the command line flag -fslp-vectorize-aggressive.
134
Tom Stellard72fffba2013-02-08 22:24:41 +0000135R600 Backend
136------------
137
138The R600 backend was added in this release, it supports AMD GPUs
139(HD2XXX - HD7XXX). This backend is used in AMD's Open Source
140graphics / compute drivers which are developed as part of the `Mesa3D
141<http://www.mesa3d.org>`_ project.
142
Richard Sandifordb11f9272013-05-07 15:52:32 +0000143SystemZ/s390x Backend
144---------------------
145
146LLVM and clang now support IBM's z/Architecture. At present this support
147is restricted to GNU/Linux (GNU triplet s390x-linux-gnu) and requires
148z10 or greater.
149
Sean Silva5672a372013-02-07 05:56:46 +0000150
Pekka Jaaskelainenb531a112013-05-03 07:37:04 +0000151External Open Source Projects Using LLVM 3.3
152============================================
153
154An exciting aspect of LLVM is that it is used as an enabling technology for
155a lot of other language and tools projects. This section lists some of the
156projects that have already been updated to work with LLVM 3.3.
157
158
159Portable Computing Language (pocl)
160----------------------------------
161
162In addition to producing an easily portable open source OpenCL
163implementation, another major goal of `pocl <http://pocl.sourceforge.net/>`_
164is improving performance portability of OpenCL programs with
165compiler optimizations, reducing the need for target-dependent manual
166optimizations. An important part of pocl is a set of LLVM passes used to
167statically parallelize multiple work-items with the kernel compiler, even in
168the presence of work-group barriers. This enables static parallelization of
169the fine-grained static concurrency in the work groups in multiple ways.
170
171TTA-based Co-design Environment (TCE)
172-------------------------------------
173
174`TCE <http://tce.cs.tut.fi/>`_ is a toolset for designing new
175processors based on the Transport triggered architecture (TTA).
176The toolset provides a complete co-design flow from C/C++
177programs down to synthesizable VHDL/Verilog and parallel program binaries.
178Processor customization points include the register files, function units,
179supported operations, and the interconnection network.
180
181TCE uses Clang and LLVM for C/C++/OpenCL C language support, target independent
182optimizations and also for parts of code generation. It generates new
183LLVM-based code generators "on the fly" for the designed TTA processors and
184loads them in to the compiler backend as runtime libraries to avoid
185per-target recompilation of larger parts of the compiler chain.
186
Sean Silva5672a372013-02-07 05:56:46 +0000187
Dmitri Gribenko38782b82012-12-09 23:14:26 +0000188Additional Information
189======================
190
191A wide variety of additional information is available on the `LLVM web page
192<http://llvm.org/>`_, in particular in the `documentation
193<http://llvm.org/docs/>`_ section. The web page also contains versions of the
194API documentation which is up-to-date with the Subversion version of the source
195code. You can access versions of these documents specific to this release by
196going into the ``llvm/docs/`` directory in the LLVM tree.
197
198If you have any questions or comments about LLVM, please feel free to contact
199us via the `mailing lists <http://llvm.org/docs/#maillist>`_.
200