[LLVMdev] 3.4.1 Release Plans

[David Fang]

Hi Tom,
 	Thanks for doing this.  I would like to nominate the following 
patches to be backported to release_34 (3.4.1).

LLVM:
r196168, r196970 -- .weak_definition vs. .weak_def_can_be_hidden
 	(r196168 is Rafael's, 970 is mine)
r196987, r197572, r197574 -- [ABI] f64,i64 alignment on ppc-darwin
 	all Rafael's, 196987 is a cosmetic change that made it easier
 	to apply the others.
r198744 [Iain Sandoe] -- FDE cross-section relocs for EH

https://github.com/fangism/llvm/tree/powerpc-darwin8-rel-3.4

- - - - - - - - - - - - - - - - - -
Clang:
r197577 [Rafael] -- f64 alignment ppc-darwin struct layout
r196981 [me] -- suppress -Q for legacy system assembler

https://github.com/fangism/clang/tree/powerpc-darwin8-rel-3.4


I have already been testing and packaging with these patches, which live 
on my 'powerpc-darwin8-rel-3.4' branch (tracks release_34), which were 
included in my own port of release-3.4.  My testing of that branch
covers powerpc-darwin8/9, i386-darwin10, x86_64-darwin11 (even though it 
is named powerpc-darwin8).  As 3.4.1 approaches, I will re-merge this 
branch for testing.

I am also currently using powerpc-darwin8-rel-3.4 as my bootstrapping 
C++11 compiler for llvm/clang trunk (3.5).


Iain and I are aware of more powerpc-darwin8 ABI issues that have not yet 
been fixed in trunk.  (Some patches exist, but not yet posted.)  As things 
stand now, the release I've made comes with this warning that 
powerpc-darwin ABI fixes are still to come, so ABI 'breakage' by 'fixing' 
is to be expected.

Your darwin-legacy co-maintainer,

David


> Hi,
>
> We are now about halfway between the 3.4 and 3.5 releases, and I would
> like to start preparing for a 3.4.1 release.  Here is my proposed release
> schedule:
>
> Mar 26 - April 9: Identify and backport additional bug fixes to the 3.4 branch.
> April 9 - April 18: Testing Phase
> April 18: 3.4.1 Release
>
> How you can help:
>
> - If you have any bug fixes you think should be included to 3.4.1, send
>  me an email with the SVN revision in trunk and also cc the code owner
>  and llvm-commits (or cfe-commits if it is a clang patch).
>
> - Start integrating the 3.4 branch into your project or OS distribution
>  to and check for any issues.
>
> - Volunteer as a tester for the testing phase.
>
> Thank you,
>
> Tom
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>

-- 
David Fang
http://www.csl.cornell.edu/~fang/