Bug 2352554
Summary: | chromium build error on ppc64le on f42 and rawhide | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Than Ngo <than> |
Component: | llvm | Assignee: | Tom Stellard <tstellar> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 42 | CC: | airlied, dmalcolm, fedora-llvm-team, jakub, jchecahi, jistone, kkleine, npopov, scottt.tw, sergesanspaille, siddharth.kde, suraj.ghimire7, tbaeder, tstellar, tuliom |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | ppc64le | ||
OS: | Linux | ||
URL: | https://kojipkgs.fedoraproject.org//work/tasks/9743/130229743/build.log | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | --- | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2025-03-31 11:46:43 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Than Ngo
2025-03-14 13:31:34 UTC
Just info for you: chromium built fine with llvm-19.1.7-11. So it looks like a regression here. In LLVM 20, the ppc64le backend started to use the GlobalMerge pass instead of a custom pass. I wonder if there are corner cases with issues. @than, could you test if the build works when passing -mno-global-merge , please? @tuliom, the build still aborts with the same error when passing -mno-global-merge @tuliom, the build works when passing -O0 (independent of -mno-global-merge option) I managed to reduce the test for this issue and reported it upstream: https://github.com/llvm/llvm-project/issues/131394 -mllvm -ppc-global-merge=0 instead of -mno-global-merge may work. (In reply to Nikita Popov from comment #6) > -mllvm -ppc-global-merge=0 instead of -mno-global-merge may work. It works with -mllvm -ppc-global-merge=0 I believe the new llvm-20.1.1-1.fc42 and llvm-20.1.1-1.fc43 builds should fix this, but I haven't verified. (In reply to Nikita Popov from comment #8) > I believe the new llvm-20.1.1-1.fc42 and llvm-20.1.1-1.fc43 builds should > fix this, but I haven't verified. I did a scratch build of chromium using llvm-20.1.1-1.fc43 and the build was successful: https://koji.fedoraproject.org/koji/taskinfo?taskID=130858088 (In reply to Tom Stellard from comment #9) > (In reply to Nikita Popov from comment #8) > > I believe the new llvm-20.1.1-1.fc42 and llvm-20.1.1-1.fc43 builds should > > fix this, but I haven't verified. > > I did a scratch build of chromium using llvm-20.1.1-1.fc43 and the build was > successful: https://koji.fedoraproject.org/koji/taskinfo?taskID=130858088 Tom, looking at the build.log i still see CXXFLAGS+=' -O0' used in your scratchbuild. I will do a scratch build without the workaround today and will report the result to you. Thanks I did a scratch build of latest chromium with llvm-20.1.1-1.fc43 and confirmed the fix. Thanks you! |