llvm dev - Feb 2020 - [10.0.0 Release] Release Candidate 2 is here

That sounds like an invasive change.

Can we revert the change that broke the Polly build instead?

On Mon, Feb 24, 2020 at 6:24 PM Michael Kruse <llvmdev at meinersbur.de>
wrote:
>
> Hi,
>
> due to the filing of http://llvm.org/PR45001 I was made be aware that
> we could face a flood of emails about Polly not working anymore. We
> could avoid that by merging https://reviews.llvm.org/D72372.
> Otherwise, as mentioned in http://llvm.org/PR45001, we'd have to
> rewrite the documentation about how to build Polly.
>
> I know this is not ideal two days before the planned release. @zmodem
> What approach do you prefer? So far I've added 45001 to the release
> blockers.
>
> Michael
>
>
> Am Do., 13. Feb. 2020 um 16:35 Uhr schrieb Hans Wennborg via llvm-dev
> <llvm-dev at lists.llvm.org>:
> >
> > Hello everyone,
> >
> > Release Candidate 2 was tagged earlier today as llvmorg-10.0.0-rc2. It
> > includes 98 commits since the previous release candidate.
> >
> > Source code and docs are available at
> > https://prereleases.llvm.org/10.0.0/#rc2 and
> > https://github.com/llvm/llvm-project/releases/tag/llvmorg-10.0.0-rc2
> >
> > Pre-built binaries will be added as they become available.
> >
> > Please file bug reports for any issues you find as blockers of
> > https://llvm.org/pr44555
> >
> > Release testers: please run the test script, share your results, and
> > upload binaries.
> >
> > I'm hoping we can now start tying up the loose ends, fixing the
> > blocking bugs, and getting the branch ready for shipping as a stable
> > release soon.
> >
> > Thanks,
> > Hans
> > _______________________________________________
> > LLVM Developers mailing list
> > llvm-dev at lists.llvm.org
> > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

Am Di., 25. Feb. 2020 um 03:55 Uhr schrieb Hans Wennborg <hans at
chromium.org>:
> That sounds like an invasive change.
It changes a default value to what it was in llvm-9. I'd consider it
relatively risk-free.

> Can we revert the change that broke the Polly build instead?
That'd be
https://reviews.llvm.org/rG24ab9b537e61b3fe5e6a1019492ff6530d82a3ee
which is an invasive change. Serge Guelton already wrote some some
fixes on top of that, others such as https://bugs.llvm.org/PR44870 are
still unfixed.

If you think this is easier, then I'd say go ahead.

Michael

Hi,

I added the change to Polly's release note in
https://github.com/llvm/llvm-project/commit/002af0119286297dbd76b08a4a6cc4b6b87d3f26
to be sure that we have some documentation, in case you decide to tag
the release as-is.

In case you decide to either revert
24ab9b537e61b3fe5e6a1019492ff6530d82a3ee or cherry-pick D72372 (I'd
prefer either over keeping as-is), could you undo the release note
change as well?

Michael

On Wed, Feb 26, 2020 at 5:49 AM Michael Kruse <llvmdev at meinersbur.de>
wrote:
>
> Hi,
>
> I added the change to Polly's release note in
>
https://github.com/llvm/llvm-project/commit/002af0119286297dbd76b08a4a6cc4b6b87d3f26
> to be sure that we have some documentation, in case you decide to tag
> the release as-is.
>
> In case you decide to either revert
> 24ab9b537e61b3fe5e6a1019492ff6530d82a3ee or cherry-pick D72372 (I'd
> prefer either over keeping as-is), could you undo the release note
> change as well?
I've gone ahead and cherry-picked D72372 and reverted the release note.

Thanks,
Hans