<li>Introduced many new warnings, including <code>-Wmissing-field-initializers</code>, <code>-Wshadow</code>, <code>-Wno-protocol</code>, <code>-Wtautological-compare</code>, <code>-Wstrict-selector-match</code>, <code>-Wcast-align</code>, <code>-Wunused</code> improvements, and greatly improved format-string checking.</li>
<li>Introduced the "libclang" library, a C interface to Clang intended to support IDE clients.</li>
<li>Added support for <code>#pragma GCC visibility</code>, <code>#pragma align</code>, and others.</li>
- <li>Added support for SSE, ARM NEON, and Altivec.</li>
+ <li>Added support for SSE, AVX, ARM NEON, and AltiVec.</li>
<li>Improved support for many Microsoft extensions.</li>
<li>Implemented support for blocks in C++.</li>
<li>Implemented precompiled headers for C++.</li>
<div class="doc_text">
<p>
-<a href="http://libc++.llvm.org/">libc++</a> is another new member of the LLVM
+<a href="http://libcxx.llvm.org/">libc++</a> is another new member of the LLVM
family. It is an implementation of the C++ standard library, written from the
ground up to specifically target the forthcoming C++'0X standard and focus on
delivering great performance.</p>
be 13 in one of the predecessors of a block. It does this in conjunction
with the new LazyValueInfo analysis pass.</li>
<li>The new RegionInfo analysis pass identifies single-entry single-exit regions
- in the CFG. You can play with it with the "opt -regions analyze" or
+ in the CFG. You can play with it with the "opt -regions -analyze" or
"opt -view-regions" commands.</li>
<li>The loop optimizer has significantly improved strength reduction and analysis
capabilities. Notably it is able to build on the trap value and signed
variables can be accessed via same base address) and potentially reducing
register pressure.</li>
-<li>The ARM has received many minor improvements and tweaks which lead to
-substantially better performance in a wide range of different scenarios.</li>
+<li>The ARM backend has received many minor improvements and tweaks which lead
+ to substantially better performance in a wide range of different scenarios.
+</li>
<li>The ARM NEON intrinsics have been substantially reworked to reduce
redundancy and improve code generation. Some of the major changes are:
LLVM. The Triple::normalize utility method has been added to help front-ends
deal with funky triples.
</li>
+<li>
+ The signature of the <tt>GCMetadataPrinter::finishAssembly</tt> virtual
+ function changed: the <tt>raw_ostream</tt> and <tt>MCAsmInfo</tt> arguments
+ were dropped. GC plugins which compute stack maps must be updated to avoid
+ having the old definition overload the new signature.
+</li>
+<li>
+ The signature of <tt>MemoryBuffer::getMemBuffer</tt> changed. Unfortunately
+ calls intended for the old version still compile, but will not work correctly,
+ leading to a confusing error about an invalid header in the bitcode.
+</li>
<li>
- Some APIs got renamed:
+ Some APIs were renamed:
<ul>
<li>llvm_report_error -> report_fatal_error</li>
<li>llvm_install_error_handler -> install_fatal_error_handler</li>
</ul>
</li>
+<li>
+ Some public headers were renamed:
+ <ul>
+ <li><tt>llvm/Assembly/AsmAnnotationWriter.h</tt> was renamed
+ to <tt>llvm/Assembly/AssemblyAnnotationWriter.h</tt>
+ </li>
+ </ul>
</ul>
</div>
+<!--=========================================================================-->
+<div class="doc_subsection">
+<a name="devtree_changes">Development Infrastructure Changes</a>
+</div>
+
+<div class="doc_text">
+
+<p>This section lists changes to the LLVM development infrastructure. This
+mostly impacts users who actively work on LLVM or follow development on
+mainline, but may also impact users who leverage the LLVM build infrastructure
+or are interested in LLVM qualification.</p>
+
+<ul>
+ <li>The default for <tt>make check</tt> is now to use
+ the <a href="http://llvm.org/cmds/lit.html">lit</a> testing tool, which is
+ part of LLVM itself. You can use <tt>lit</tt> directly as well, or use
+ the <tt>llvm-lit</tt> tool which is created as part of a Makefile or CMake
+ build (and knows how to find the appropriate tools). See the <tt>lit</tt>
+ documentation and the <a href="http://blog.llvm.org/2009/12/lit-it.html">blog
+ post</a>, and <a href="http://llvm.org/bugs/show_bug.cgi?id=5217">PR5217</a>
+ for more information.</li>
+
+ <li>The LLVM <tt>test-suite</tt> infrastructure has a new "simple" test format
+ (<tt>make TEST=simple</tt>). The new format is intended to require only a
+ compiler and not a full set of LLVM tools. This makes it useful for testing
+ released compilers, for running the test suite with other compilers (for
+ performance comparisons), and makes sure that we are testing the compiler as
+ users would see it. The new format is also designed to work using reference
+ outputs instead of comparison to a baseline compiler, which makes it run much
+ faster and makes it less system dependent.</li>
+
+ <li>Significant progress has been made on a new interface to running the
+ LLVM <tt>test-suite</tt> (aka the LLVM "nightly tests") using
+ the <a href="http://llvm.org/docs/lnt">LNT</a> infrastructure. The LNT
+ interface to the <tt>test-suite</tt> brings significantly improved reporting
+ capabilities for monitoring the correctness and generated code quality
+ produced by LLVM over time.</li>
+</ul>
+</div>
<!-- *********************************************************************** -->
<div class="doc_section">
href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">LLVMdev list</a>.</p>
<ul>
-<li>The Alpha, Blackfin, CellSPU, MicroBlaze, MSP430, MIPS, PIC16, SystemZ
+<li>The Alpha, Blackfin, CellSPU, MicroBlaze, MSP430, MIPS, SystemZ
and XCore backends are experimental.</li>
<li><tt>llc</tt> "<tt>-filetype=obj</tt>" is experimental on all targets
other than darwin-i386 and darwin-x86_64.</li>
projects / oota-llvm.git / blobdiff