ReleaseNotes.rst 7.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184
  1. =========================
  2. LLVM 10.0.0 Release Notes
  3. =========================
  4. .. contents::
  5. :local:
  6. .. warning::
  7. These are in-progress notes for the upcoming LLVM 10 release.
  8. Release notes for previous releases can be found on
  9. `the Download Page <https://releases.llvm.org/download.html>`_.
  10. Introduction
  11. ============
  12. This document contains the release notes for the LLVM Compiler Infrastructure,
  13. release 10.0.0. Here we describe the status of LLVM, including major improvements
  14. from the previous release, improvements in various subprojects of LLVM, and
  15. some of the current users of the code. All LLVM releases may be downloaded
  16. from the `LLVM releases web site <https://llvm.org/releases/>`_.
  17. For more information about LLVM, including information about the latest
  18. release, please check out the `main LLVM web site <https://llvm.org/>`_. If you
  19. have questions or comments, the `LLVM Developer's Mailing List
  20. <https://lists.llvm.org/mailman/listinfo/llvm-dev>`_ is a good place to send
  21. them.
  22. Note that if you are reading this file from a Subversion checkout or the main
  23. LLVM web page, this document applies to the *next* release, not the current
  24. one. To see the release notes for a specific release, please see the `releases
  25. page <https://llvm.org/releases/>`_.
  26. Non-comprehensive list of changes in this release
  27. =================================================
  28. .. NOTE
  29. For small 1-3 sentence descriptions, just add an entry at the end of
  30. this list. If your description won't fit comfortably in one bullet
  31. point (e.g. maybe you would like to give an example of the
  32. functionality, or simply have a lot to talk about), see the `NOTE` below
  33. for adding a new subsection.
  34. * The ISD::FP_ROUND_INREG opcode and related code was removed from SelectionDAG.
  35. * Enabled MemorySSA as a loop dependency. Since
  36. `r370957 <https://reviews.llvm.org/rL370957>`_
  37. (`D58311 <https://reviews.llvm.org/D58311>`_ ``[MemorySSA & LoopPassManager]
  38. Enable MemorySSA as loop dependency. Update tests.``), the MemorySSA analysis
  39. is being preserved and used by a series of loop passes. The most significant
  40. use is in LICM, where the instruction hoisting and sinking relies on aliasing
  41. information provided by MemorySSA vs previously creating an AliasSetTracker.
  42. The LICM step of promoting variables to scalars still relies on the creation
  43. of an AliasSetTracker, but its use is reduced to only be enabled for loops
  44. with a small number of overall memory instructions. This choice was motivated
  45. by experimental results showing compile and run time benefits or replacing the
  46. AliasSetTracker usage with MemorySSA without any performance penalties.
  47. The fact that MemorySSA is now preserved by and available in a series of loop
  48. passes, also opens up opportunities for its use in those respective passes.
  49. .. NOTE
  50. If you would like to document a larger change, then you can add a
  51. subsection about it right here. You can copy the following boilerplate
  52. and un-indent it (the indentation causes it to be inside this comment).
  53. Special New Feature
  54. -------------------
  55. Makes programs 10x faster by doing Special New Thing.
  56. * As per :ref:`LLVM Language Reference Manual <i_getelementptr>`,
  57. ``getelementptr inbounds`` can not change the null status of a pointer,
  58. meaning it can not produce non-null pointer given null base pointer, and
  59. likewise given non-null base pointer it can not produce null pointer; if it
  60. does, the result is a :ref:`poison value <poisonvalues>`.
  61. Since `r369789 <https://reviews.llvm.org/rL369789>`_
  62. (`D66608 <https://reviews.llvm.org/D66608>`_ ``[InstCombine] icmp eq/ne (gep
  63. inbounds P, Idx..), null -> icmp eq/ne P, null``) LLVM uses that for
  64. transformations. If the original source violates these requirements this
  65. may result in code being miscompiled. If you are using Clang front-end,
  66. Undefined Behaviour Sanitizer ``-fsanitize=pointer-overflow`` check
  67. will now catch such cases.
  68. * The Loop Idiom Recognition (``-loop-idiom``) pass has learned to recognize
  69. ``bcmp`` pattern, and convert it into a call to ``bcmp`` (or ``memcmp``)
  70. function.
  71. Changes to the LLVM IR
  72. ----------------------
  73. * Unnamed function arguments now get printed with their automatically
  74. generated name (e.g. "i32 %0") in definitions. This may require front-ends
  75. to update their tests; if so there is a script utils/add_argument_names.py
  76. that correctly converted 80-90% of Clang tests. Some manual work will almost
  77. certainly still be needed.
  78. Changes to building LLVM
  79. ------------------------
  80. Changes to the ARM Backend
  81. --------------------------
  82. During this release ...
  83. Changes to the MIPS Target
  84. --------------------------
  85. During this release ...
  86. Changes to the PowerPC Target
  87. -----------------------------
  88. During this release ...
  89. Changes to the X86 Target
  90. -------------------------
  91. During this release ...
  92. * Less than 128 bit vector types, v2i32, v4i16, v2i16, v8i8, v4i8, and v2i8, are
  93. now stored in the lower bits of an xmm register and the upper bits are
  94. undefined. Previously the elements were spread apart with undefined bits in
  95. between them.
  96. * v32i8 and v64i8 vectors with AVX512F enabled, but AVX512BW disabled will now
  97. be passed in ZMM registers for calls and returns. Previously they were passed
  98. in two YMM registers. Old behavior can be enabled by passing
  99. -x86-enable-old-knl-abi
  100. * -mprefer-vector-width=256 is now the default behavior skylake-avx512 and later
  101. Intel CPUs. This tries to limit the use of 512-bit registers which can cause a
  102. decrease in CPU frequency on these CPUs. This can be re-enabled by passing
  103. -mprefer-vector-width=512 to clang or passing -mattr=-prefer-256-bit to llc.
  104. Changes to the AMDGPU Target
  105. -----------------------------
  106. Changes to the AVR Target
  107. -----------------------------
  108. During this release ...
  109. * Deprecated the mpx feature flag for the Intel MPX instructions. There were no
  110. intrinsics for this feature. This change only this effects the results
  111. returned by getHostCPUFeatures on CPUs that implement the MPX instructions.
  112. Changes to the WebAssembly Target
  113. ---------------------------------
  114. During this release ...
  115. Changes to the OCaml bindings
  116. -----------------------------
  117. Changes to the C API
  118. --------------------
  119. Changes to the DAG infrastructure
  120. ---------------------------------
  121. Changes to LLDB
  122. ===============
  123. External Open Source Projects Using LLVM 10
  124. ===========================================
  125. * A project...
  126. Additional Information
  127. ======================
  128. A wide variety of additional information is available on the `LLVM web page
  129. <https://llvm.org/>`_, in particular in the `documentation
  130. <https://llvm.org/docs/>`_ section. The web page also contains versions of the
  131. API documentation which is up-to-date with the Subversion version of the source
  132. code. You can access versions of these documents specific to this release by
  133. going into the ``llvm/docs/`` directory in the LLVM tree.
  134. If you have any questions or comments about LLVM, please feel free to contact
  135. us via the `mailing lists <https://llvm.org/docs/#mailing-lists>`_.