[LLVMdev] !!! 3.2 Release RC2 deadline November 29th
Pawel Wodnicki
root at 32bitmicro.com
Tue Nov 27 19:35:15 PST 2012
Hello,
Just a quick reminder that the November 29th (10p.m. PST) is the
end of Phase 1 testing and Release Candidate 2 (RC2) deadline.
After RC2 deadline, LLVM-Clang 3.2 release will be considered feature
complete and no new functionality can be added.
With 2 days left please use following guidelines when
initiating request for patches before RC2 deadline.
I will be happy to merge *approved* patches for low risk/
crash fixes that merge cleanly and have simple test case or
procedure to verify correctness (aka 1040 EZ Patch).
Patches that do not fall under the above category need to
be classified as either release blocking (discussed below)
or non release blocking and thus not included in this release.
Code owners
I need your input on the state of the release blocking issues as
listed in the Bug 13893 - "Umbrella bug for 3.2 release"
http://llvm.org/bugs/show_bug.cgi?id=13893.
Please review the list below and let me know whether the
listed bugs can be (better yet will be!) fixed in the Phase 2.
If there are other release stopping bugs/issues that you
think should be fixed before the final 3.2 release but
are not listed below then please add them to the
Bug 13893 - "Umbrella bug for 3.2 release".
As of today Tuesday Nov 27th following release blocking
bugs are still open:
12664 - O2 -ftree-vectorize -fplugin-arg-dragonegg-enable-gcc-optzns on
mdbx.f90 confuses dragoneg
13561 - LLVM ERROR: Cannot select: 0x14214bb10: i16 =
extract_vector_elt 0x14214b910, 0x142142c10
14116 - Inliner incorrectly combines cleanup and catch landing pads
14279 - mishandling of implicit move in class with copy-only member
14337 - UNREACHABLE executed at CallingConvLower.cpp:111 when returning
v4f64 on ARM
14429 - Dragonegg fails to build clang
Pawel
More information about the llvm-dev
mailing list