[LLVMdev] [cfe-dev] !!! 3.2 Release RC2 deadline November 29th

Duncan Sands baldrick at free.fr
Wed Nov 28 21:01:22 PST 2012


Hi Tanya,

>> 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
>>
>
> No action on this bug in 4 months. I don't think It shouldn't be a release blocker either.

I have a fix!

>
>> 14116 - Inliner incorrectly combines cleanup and catch landing pads
>>
>
> I think this one can be moved out as a release blocker. Too much debate and no action on the bug in over a month.
>
>> 14279 - mishandling of implicit move in class with copy-only member
>>
>
> This would be nice to have, but is self-host in C++11 mode currently tested by the build bots?
>
>> 14337 - UNREACHABLE executed at CallingConvLower.cpp:111 when returning
>> v4f64 on ARM
>>
>
> A great bug to fix, but ARM is not a supported target for release criteria unless someone wants to make this happen for 3.3. So unless it gets fixed soon, it shouldn't block the release.
>
>> 14429 - Dragonegg fails to build clang
>>
>
> Dragonegg is a part of the release, but my question is.. is bootstrap only tested at release time (seems like some buildbots must test this)? This should be changed for 3.3. This seems like a more likely candidate to get fixed for 3.2 though.

Dragonegg+LLVM+GCC is bootstrapped on every commit.  However the bootstrap
doesn't include clang, which is a mistake.

Ciao, Duncan.

>
> Thanks for all your hard work with the release!
>
> -Tanya
>
>>
>> Pawel
>> _______________________________________________
>> cfe-dev mailing list
>> cfe-dev at cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>




More information about the llvm-dev mailing list