Closed Bug 1521129 Opened 6 years ago Closed 6 years ago

Bump clang-cl to 8.0.0 release branch for arm64 support

Categories

(Firefox Build System :: Toolchains, enhancement)

enhancement
Not set
normal

Tracking

(firefox66 fixed)

RESOLVED FIXED
mozilla66
Tracking Status
firefox66 --- fixed

People

(Reporter: away, Assigned: away)

References

Details

Attachments

(1 file)

47 bytes, text/x-phabricator-request
Details | Review

Bug 1512822 will require that we use at least LLVM 8.0.0 rc1.

The sidebar on llvm.org's front page is currently projecting:

8.0.0:
Jan 16: Branch point, rc1
Feb 6: rc2
Feb 27: final

(Though historically the dates have not always been exact.)

According to the Firefox release calendar, we have merge days on 2019-01-28 (Fx67) and 2019-03-18 (Fx68).

I propose that in the first days of Firefox 67, we take whatever LLVM RC is current, and later within 67 pick up the final release.

Depends on: 1521133

I'm getting the following linker error in libxul when trying to build with rc1 and ThinLTO:

LLVM ERROR: Associative COMDAT symbol '??_7MaxExpSink@?A0xC8782BCA@icu_63@@6B@' does not exist.

(In reply to Michael Woerister from comment #2)

I'm getting the following linker error in libxul when trying to build with
rc1 and ThinLTO:

LLVM ERROR: Associative COMDAT symbol
'??_7MaxExpSink@?A0xC8782BCA@icu_63@@6B@' does not exist.

Do you have a link to a try push? (Not necessary but it would be the most concise way to reproduce your state.) Otherwise, can you share your mozconfig, LLVM and Mozilla revisions, and any patches you have applied?

Attachment #9037643 - Attachment description: Bump clang-cl to 8.0.0 release branch → Bump clang-cl to 8.0.0 rc1
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla66
Depends on: 1522771
Assignee: nobody → dmajor
Blocks: 1516543
Depends on: 1524087
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: