blob: 8dc16813580ebe55151d9ea3efdb894a43e5d645 [file] [log] [blame]
Dmitri Gribenko38782b82012-12-09 23:14:26 +00001======================
Bill Wendling70d39e62013-11-20 10:10:50 +00002LLVM 3.5 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::
Bill Wendling70d39e62013-11-20 10:10:50 +00009 These are in-progress notes for the upcoming LLVM 3.5 release. You may
10 prefer the `LLVM 3.4 Release Notes <http://llvm.org/releases/3.4/docs
Sean Silva1eab30d2013-01-20 03:29:50 +000011 /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,
Bill Wendling70d39e62013-11-20 10:10:50 +000018release 3.5. 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
Rafael Espindola1840ad42014-01-10 22:06:26 +000037* All backends have been changed to use the MC asm printer and support for the
38 non MC one has been removed.
39
Venkatraman Govindaraju5a96c872014-02-03 15:28:26 +000040* Clang can now successfully self-host itself on Linux/Sparc64 and on
41 FreeBSD/Sparc64.
42
Rafael Espindolab4eec1d2014-02-05 18:00:21 +000043* LLVM now assumes the assembler supports ``.loc`` for generating debug line
44 numbers. The old support for printing the debug line info directly was only
45 used by ``llc`` and has been removed.
46
Daniel Sanders66d797a2014-02-20 09:24:15 +000047* All inline assembly is parsed by the integrated assembler when it is enabled.
48 Previously this was only the case for object-file output. It is now the case
Rafael Espindola48fa6ed2014-02-21 03:13:54 +000049 for assembly output as well. The integrated assembler can be disabled with
50 the ``-no-integrated-as`` option,
Daniel Sanders66d797a2014-02-20 09:24:15 +000051
Rafael Espindolaa51f0f82014-02-28 02:17:23 +000052* llvm-ar now handles IR files like regular object files. In particular, a
53 regular symbol table is created for symbols defined in IR files.
54
Rafael Espindola1e312c72014-05-05 17:53:29 +000055* LLVM now always uses cfi directives for producing most stack
56 unwinding information.
Rafael Espindola595f5422014-05-05 17:33:26 +000057
Sean Silva1eab30d2013-01-20 03:29:50 +000058.. NOTE
59 For small 1-3 sentence descriptions, just add an entry at the end of
60 this list. If your description won't fit comfortably in one bullet
61 point (e.g. maybe you would like to give an example of the
62 functionality, or simply have a lot to talk about), see the `NOTE` below
63 for adding a new subsection.
Dmitri Gribenko38782b82012-12-09 23:14:26 +000064
Sean Silva1eab30d2013-01-20 03:29:50 +000065* ... next change ...
Dmitri Gribenko38782b82012-12-09 23:14:26 +000066
Sean Silva1eab30d2013-01-20 03:29:50 +000067.. NOTE
68 If you would like to document a larger change, then you can add a
69 subsection about it right here. You can copy the following boilerplate
70 and un-indent it (the indentation causes it to be inside this comment).
Dmitri Gribenko38782b82012-12-09 23:14:26 +000071
Sean Silva1eab30d2013-01-20 03:29:50 +000072 Special New Feature
73 -------------------
Dmitri Gribenko38782b82012-12-09 23:14:26 +000074
Sean Silva1eab30d2013-01-20 03:29:50 +000075 Makes programs 10x faster by doing Special New Thing.
Dmitri Gribenko38782b82012-12-09 23:14:26 +000076
Renato Golin7c9d0502014-03-18 10:16:15 +000077Changes to the ARM Backend
78--------------------------
79
80Since release 3.3, a lot of new features have been included in the ARM
81back-end but weren't production ready (ie. well tested) on release 3.4.
82Just after the 3.4 release, we started heavily testing two major parts
83of the back-end: the integrated assembler (IAS) and the ARM exception
84handling (EHABI), and now they are enabled by default on LLVM/Clang.
85
86The IAS received a lot of GNU extensions and directives, as well as some
87specific pre-UAL instructions. Not all remaining directives will be
88implemented, as we made judgement calls on the need versus the complexity,
89and have chosen simplicity and future compatibility where hard decisions
90had to be made. The major difference is, as stated above, the IAS validates
91all inline ASM, not just for object emission, and that cause trouble with
92some uses of inline ASM as pre-processor magic.
93
94So, while the IAS is good enough to compile large projects (including most
95of the Linux kernel), there are a few things that we can't (and probably
96won't) do. For those cases, please use ``-fno-integrated-as`` in Clang.
97
98Exception handling is another big change. After extensive testing and
99changes to cooperate with Dwarf unwinding, EHABI is enabled by default.
100The options ``-arm-enable-ehabi`` and ``-arm-enable-ehabi-descriptors``,
101which were used to enable EHABI in the previous releases, are removed now.
102
103This means all ARM code will emit EH unwind tables, or CFI unwinding (for
104debug/profiling), or both. To avoid run-time inconsistencies, C code will
105also emit EH tables (in case they interoperate with C++ code), as is the
Renato Golin3a077eb2014-03-24 11:02:38 +0000106case for other architectures (ex. x86_64).
Renato Golin7c9d0502014-03-18 10:16:15 +0000107
Bill Wendling70d39e62013-11-20 10:10:50 +0000108External Open Source Projects Using LLVM 3.5
Pekka Jaaskelainenb531a112013-05-03 07:37:04 +0000109============================================
110
111An exciting aspect of LLVM is that it is used as an enabling technology for
112a lot of other language and tools projects. This section lists some of the
Bill Wendling70d39e62013-11-20 10:10:50 +0000113projects that have already been updated to work with LLVM 3.5.
Kai Nackeec6e3922013-11-14 05:57:40 +0000114
115
Dmitri Gribenko38782b82012-12-09 23:14:26 +0000116Additional Information
117======================
118
119A wide variety of additional information is available on the `LLVM web page
120<http://llvm.org/>`_, in particular in the `documentation
121<http://llvm.org/docs/>`_ section. The web page also contains versions of the
122API documentation which is up-to-date with the Subversion version of the source
123code. You can access versions of these documents specific to this release by
124going into the ``llvm/docs/`` directory in the LLVM tree.
125
126If you have any questions or comments about LLVM, please feel free to contact
127us via the `mailing lists <http://llvm.org/docs/#maillist>`_.
128