1670686 - Update to clang 11.0.0 final release

Status: RESOLVED FIXED

(Firefox Build System :: Toolchains, enhancement)

Description

[(Away)]

https://lists.llvm.org/pipermail/llvm-dev/2020-October/145750.html

Comment 1

[(Away)]

Attachment: Update to clang 11.0.0 final release

The llvmorg-11.0.0 release was tagged today at 176249bd.

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/de0d801e6fb8
Update to clang 11.0.0 final release r=firefox-build-system-reviewers,andi,rstewart

Comment 3

[Natalia Csoregi [:nataliaCs]]

https://hg.mozilla.org/mozilla-central/rev/de0d801e6fb8

Comment 4

[(Away)]

Comment on attachment 9181034 [details]
Update to clang 11.0.0 final release

@jcristau: This uplift is not required but I wanted to see what you think. I'm a little bit uncomfortable changing a compiler so close to release. There's an argument that we've put more testing on the current RC3 even if it is not final. On the other hand, maybe there's some latent bug that has been fixed between RC3 and final. It's hard to say without a crystal ball which is less risky. Since you deal with uplifts much more frequently, I figure you have a more reliable sense about this topic than me.

Beta/Release Uplift Approval Request

• User impact if declined: Inconsistent compiler versus nightly + incomplete release candidate (== probably harmless but I don't know)
• Is this code covered by automated tests?: Unknown
• Has the fix been verified in Nightly?: No
• Needs manual test from QE?: No
• If yes, steps to reproduce:
• List of other uplifts needed: None
• Risk to taking this patch: Medium
• Why is the change risky/not risky? (and alternatives if risky): See note above
• String changes made/needed: none

Comment 5

[Julien Cristau [:jcristau]]

Comment on attachment 9181034 [details]
Update to clang 11.0.0 final release

we've already built a release candidate for 82, let's not take that risk now