llvm dev - Apr 2013 - [LLVMdev] [Announcement] 3.3 Release Planning!

Happy April!

[Contrary to the day, this is not an April Fool's joke. ;-)]

It has been several months since the release of Clang 3.2. Now is the time to
start thinking about the next release! The (very) tentative schedule is testing
in May and a release in June.

What This Means For You

Now is the time to start thinking about which features you are currently working
on and getting them wrapped up. As usual, we will be cutting our branch near the
beginning of May. At that point, all new features should be mostly complete. Any
patches accepted after we branch must be only of a clean-up or bug fix nature.

Supported Platforms & A Call For Testers

This is also the time to start thinking about which platforms we want to
support. We currently support the following platforms:

• MacOS X (x86)
• Linux (Ubuntu - x86)
• FreeBSD (x86)
• Windows (experimentally)

We would like to support ARM again. Also, there has been significant
improvements on other platforms. The only thing keeping us from releasing
binaries for non-Intel platforms is a phalanx of testers for those platforms.
The more testers we have, the better.

Because LLVM is an open source project, we rely upon the community members'
copious spare time to help us push the release out. Not only do we need testers
for new platforms, we also need testers for platforms we currently support.
Please email me directly if you are interested in becoming a tester.

What does it take to be a tester? I'm glad you asked! You are volunteering
your time and resources to test each release candidate. You are given a week to
compile the release candidate in a bootstrap build (a script is provided). You
then have to run the regression tests and the full test suite, and compare the
results from the test suite run to those of the previous release. Any
regressions need to be reported as quickly as possible so that people can fix
them. You then send the binaries to me so that I can post them for external
developers. Rinse. Repeat.

There are normally two rounds of testing. If something major comes up during the
second round of testing, we will need a third round. But we try to avoid that as
much as possible.

The last step is to package up the binaries so that they can be uploaded to the
llvm.org website.

And that's it!

As May approaches, I'll send out a more solidified schedule for the release.
I'll also begin warning people of the impending doom^H^H^H^Hbranching.

Cheers!!
-bw

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20130401/4a813916/attachment.html>

On Mon, Apr 01, 2013 at 02:05:22PM -0700, Bill Wendling
wrote:
> This is also the time to start thinking about which platforms we want to
support. We currently support the following platforms:
Let's add NetBSD(x86) to that list at least :)

The biggest problem I see right now is that we had a number of VM usage
regressions since 3.2. I am running pkgsrc bulk builds with Clang as
compiler and an address space limit of 2GB. A number of new failures
started to pop up recently. I can extract the specific failures, if
there is interest.

Joerg

On 1 April 2013 22:05, Bill Wendling <wendling at apple.com> wrote:
> We would like to support ARM again.
>
Hi Bill,

Glad you asked! ;)

I'm getting the test-suite bot green (a few minor tweaks and we're good)
and that should get us well ahead of what we've ever been on ARM. Though,
bootstrapping seem to fails a few check-all tests. I'll look into that as
soon as the test-suite bot is fully green.

Just to make sure we're talking about the same things, the requirements for
release are:

* Green direct check-all (clang-native-arm-cortex-a9 bot, green)
* Green direct test-suite (clang-native-arm-lnt bot, almost green)
* Green self-host check-all (no bot yet, some failures, will look into it
next)
* Green self-host test-suite?
* Anything else?

I don't want to have this for release-only, but as continuous integration.
Though, I hope it'll be good for all future releases.

It's probably best to produce the binaries on a Cortex-A9 (Panda ES), since
they're the most common target and the binaries work quite well on A15s.

Sylvestre,

If we do end up creating ARM binaries for the general public, your input
and expertise will be greatly appreciated! ;)

cheers,
--renato
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20130403/624b18d0/attachment.html>

On 1 Apr 2013, at 22:05, Bill Wendling <wendling at apple.com> wrote:
> • MacOS X (x86)
> • Linux (Ubuntu - x86)
> • FreeBSD (x86)
> • Windows (experimentally)
> 
> We would like to support ARM again. Also, there has been significant
improvements on other platforms. The only thing keeping us from releasing
binaries for non-Intel platforms is a phalanx of testers for those platforms.
The more testers we have, the better.
We are currently in the process of switching FreeBSD/ARM over to clang.  We will
certainly do testing, but I'm not sure it's worth LLVM shipping
binaries, as clang 3.3 will be the system compiler and clang trunk is available
in ports.

We'd also like to switch MIPS and PowerPC soon, but I believe there are
still some minor issues with PowerPC and more significant ones in MIPS, so
that's probably more in the 3.4 timeframe.
> It's probably best to produce the binaries on a Cortex-A9 (Panda ES),
since they're the most common target and the binaries work quite well on
A15s.
We still support Cortex-A8 platforms, and one of the most widely deployed ARM
platforms for us at the moment is the Raspberry Pi, which is ARM11.  I have one
sitting on my desk doing nothing at the moment, which could probably be hooked
up to the network and used for LLVM builds, although a clean build will probably
take about 24 hours on it.

David

On 03/04/2013 11:07, Renato Golin wrote:
> On 1 April 2013 22:05, Bill Wendling <wendling at apple.com
> <mailto:wendling at apple.com>> wrote:
> 
>     We would like to support ARM again.
> 
> 
> Hi Bill,
> 
> Glad you asked! ;)
[...]
> Sylvestre,
> 
> If we do end up creating ARM binaries for the general public, your input
> and expertise will be greatly appreciated! ;)
I will be happy to provide some Debian & Ubuntu ARM packages. I just
need access to ARM server(s).

Thanks,
Sylvestre

On Apr 3, 2013, at 2:07 AM, Renato Golin <renato.golin at linaro.org>
wrote:
> On 1 April 2013 22:05, Bill Wendling <wendling at apple.com> wrote:
> We would like to support ARM again.
> 
> Hi Bill,
> 
> Glad you asked! ;)
> 
> I'm getting the test-suite bot green (a few minor tweaks and we're
good) and that should get us well ahead of what we've ever been on ARM.
Though, bootstrapping seem to fails a few check-all tests. I'll look into
that as soon as the test-suite bot is fully green.
> 
> Just to make sure we're talking about the same things, the requirements
for release are:
> 
> * Green direct check-all (clang-native-arm-cortex-a9 bot, green)
> * Green direct test-suite (clang-native-arm-lnt bot, almost green)
> * Green self-host check-all (no bot yet, some failures, will look into it
next)
All of this, yes. :)
> * Green self-host test-suite?
This would be nice.
> * Anything else?
The above are pretty much the requirements for other binaries. Of course, I
expect (hope?) that the community will take each release candidate and test
their own code with it.
> I don't want to have this for release-only, but as continuous
integration. Though, I hope it'll be good for all future releases.
> 
I do too. The progress you're making is great!
> It's probably best to produce the binaries on a Cortex-A9 (Panda ES),
since they're the most common target and the binaries work quite well on
A15s.
> 
I agree. Though I'll also let Jim and Evan chime in on what they think.

Thank you!
-bw
> Sylvestre,
> 
> If we do end up creating ARM binaries for the general public, your input
and expertise will be greatly appreciated! ;)
> 
+1 :)

On Wed, Apr 03, 2013 at 10:24:13AM +0100, David Chisnall
wrote:
> On 1 Apr 2013, at 22:05, Bill Wendling <wendling at apple.com> wrote:
> 
> > • MacOS X (x86)
> > • Linux (Ubuntu - x86)
> > • FreeBSD (x86)
> > • Windows (experimentally)
> > 
> > We would like to support ARM again. Also, there has been significant
improvements on other platforms. The only thing keeping us from releasing
binaries for non-Intel platforms is a phalanx of testers for those platforms.
The more testers we have, the better.
> 
> We are currently in the process of switching FreeBSD/ARM over to clang.  We
will certainly do testing, but I'm not sure it's worth LLVM shipping
binaries, as clang 3.3 will be the system compiler and clang trunk is available
in ports.
  I think the arm binary is for linux. :)
 
Regards,
chenwj

-- 
Wei-Ren Chen (陳韋任)
Computer Systems Lab, Institute of Information Science,
Academia Sinica, Taiwan (R.O.C.)
Tel:886-2-2788-3799 #1667
Homepage: http://people.cs.nctu.edu.tw/~chenwj

It is very exciting to see experimental Windows support listed for 3.3.

Is there documentation somewhere that tracks what works and what doesn't in
this configuration, particularly for C++?. Otherwise it is difficult for
those not actively involved in developing Windows support to know what to
expect when experimenting.

Thanks,
Andrew



On Mon, Apr 1, 2013 at 5:05 PM, Bill Wendling <wendling at apple.com>
wrote:
> Happy April!
>
> [Contrary to the day, this is not an April Fool's joke. ;-)]
>
> It has been several months since the release of Clang 3.2. Now is the time
> to start thinking about the next release! The (very) tentative schedule is
> testing in May and a release in June.
>
> *What This Means For You*
> *
> *
> Now is the time to start thinking about which features you are currently
> working on and getting them wrapped up. As usual, we will be cutting our
> branch near the beginning of May. At that point, all new features should be
> mostly complete. Any patches accepted after we branch must be only of a
> clean-up or bug fix nature.
>
> *Supported Platforms & A Call For Testers*
>
> This is also the time to start thinking about which platforms we want to
> support. We currently support the following platforms:
>
> • MacOS X (x86)
> • Linux (Ubuntu - x86)
> • FreeBSD (x86)
> • Windows (experimentally)
>
> We would like to support ARM again. Also, there has been significant
> improvements on other platforms. The only thing keeping us from releasing
> binaries for non-Intel platforms is a phalanx of testers for those
> platforms. The more testers we have, the better.
>
> Because LLVM is an open source project, we rely upon the community
> members' copious spare time to help us push the release out. Not only
do we
> need testers for new platforms, we also need testers for platforms we
> currently support. Please email me directly if you are interested in
> becoming a tester.
>
> What does it take to be a tester? I'm glad you asked! You are
volunteering
> your time and resources to test each release candidate. You are given a
> week to compile the release candidate in a bootstrap build (a script is
> provided). You then have to run the regression tests and the full test
> suite, and compare the results from the test suite run to those of the
> previous release. Any regressions need to be reported as quickly as
> possible so that people can fix them. You then send the binaries to me so
> that I can post them for external developers. Rinse. Repeat.
>
> There are normally two rounds of testing. If something major comes up
> during the second round of testing, we will need a third round. But we try
> to avoid that as much as possible.
>
> The last step is to package up the binaries so that they can be uploaded
> to the llvm.org website.
>
> And that's it!
>
> As May approaches, I'll send out a more solidified schedule for the
> release. I'll also begin warning people of the impending
> doom^H^H^H^Hbranching.
>
> Cheers!!
> -bw
>
>
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20130409/2a5fe2bd/attachment.html>

Hi Andrew,

Anton is the maintainer of the Windows port. I've CC'ed him to this
email so that he can comment.

-bw

On Apr 9, 2013, at 9:48 AM, Andrew C. Morrow <andrew.c.morrow at
gmail.com> wrote:
> It is very exciting to see experimental Windows support listed for 3.3.
> 
> Is there documentation somewhere that tracks what works and what
doesn't in this configuration, particularly for C++?. Otherwise it is
difficult for those not actively involved in developing Windows support to know
what to expect when experimenting.
> 
> Thanks,
> Andrew
> 
> 
> 
> On Mon, Apr 1, 2013 at 5:05 PM, Bill Wendling <wendling at apple.com>
wrote:
> Happy April!
> 
> [Contrary to the day, this is not an April Fool's joke. ;-)]
> 
> It has been several months since the release of Clang 3.2. Now is the time
to start thinking about the next release! The (very) tentative schedule is
testing in May and a release in June.
> 
> What This Means For You
> 
> Now is the time to start thinking about which features you are currently
working on and getting them wrapped up. As usual, we will be cutting our branch
near the beginning of May. At that point, all new features should be mostly
complete. Any patches accepted after we branch must be only of a clean-up or bug
fix nature.
> 
> Supported Platforms & A Call For Testers
> 
> This is also the time to start thinking about which platforms we want to
support. We currently support the following platforms:
> 
> • MacOS X (x86)
> • Linux (Ubuntu - x86)
> • FreeBSD (x86)
> • Windows (experimentally)
> 
> We would like to support ARM again. Also, there has been significant
improvements on other platforms. The only thing keeping us from releasing
binaries for non-Intel platforms is a phalanx of testers for those platforms.
The more testers we have, the better.
> 
> Because LLVM is an open source project, we rely upon the community
members' copious spare time to help us push the release out. Not only do we
need testers for new platforms, we also need testers for platforms we currently
support. Please email me directly if you are interested in becoming a tester.
> 
> What does it take to be a tester? I'm glad you asked! You are
volunteering your time and resources to test each release candidate. You are
given a week to compile the release candidate in a bootstrap build (a script is
provided). You then have to run the regression tests and the full test suite,
and compare the results from the test suite run to those of the previous
release. Any regressions need to be reported as quickly as possible so that
people can fix them. You then send the binaries to me so that I can post them
for external developers. Rinse. Repeat.
> 
> There are normally two rounds of testing. If something major comes up
during the second round of testing, we will need a third round. But we try to
avoid that as much as possible.
> 
> The last step is to package up the binaries so that they can be uploaded to
the llvm.org website.
> 
> And that's it!
> 
> As May approaches, I'll send out a more solidified schedule for the
release. I'll also begin warning people of the impending
doom^H^H^H^Hbranching.
> 
> Cheers!!
> -bw
> 
> 
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20130409/92bf6ffe/attachment.html>