Description of problem: Latest Firefox fails to build on all Fedoras (32 -> 35). Builds are here: https://koji.fedoraproject.org/koji/taskinfo?taskID=64409024 https://koji.fedoraproject.org/koji/taskinfo?taskID=64409029 https://koji.fedoraproject.org/koji/taskinfo?taskID=64408945 https://koji.fedoraproject.org/koji/taskinfo?taskID=64409052 Error message: warning: cc1plus: out of memory allocating 8720 bytes after a total of 363249664 bytes error: failed to run custom build command for `swgl v0.1.0 (/builddir/build/BUILD/firefox-87.0/gfx/wr/swgl)` Caused by: process didn't exit successfully: `/builddir/build/BUILD/firefox-87.0/objdir/release/build/swgl-a28454d3c7c89483/build-script-build` (exit code: 1) --- stdout cargo:rerun-if-changed=/builddir/build/BUILD/firefox-87.0/gfx/wr/webrender/res/brush_blend.glsl cargo:rerun-if-changed=/builddir/build/BUILD/firefox-87.0/gfx/wr/webrender/res/shared.glsl cargo:rerun-if-changed=/builddir/build/BUILD/firefox-87.0/gfx/wr/webrender/res/base.glsl cargo:rerun-if-changed=/builddir/build/BUILD/firefox-87.0/gfx/wr/webrender/res/prim_shared.glsl cargo:rerun-if-changed=/builddir/build/BUILD/firefox-87.0/gfx/wr/webrender/res/rect.glsl cargo:rerun-if-changed=/builddir/build/BUILD/firefox-87.0/gfx/wr/webrender/res/render_task.glsl cargo:rerun-if-changed=/builddir/build/BUILD/firefox-87.0/gfx/wr/webrender/res/gpu_cache.glsl cargo:rerun-if-changed=/builddir/build/BUILD/firefox-87.0/gfx/wr/webrender/res/transform.glsl cargo:rerun-if-changed=/builddir/build/BUILD/firefox-87.0/gfx/wr/webrender/res/brush.glsl OPT_LEVEL = Some("2") TARGET = Some("armv7-unknown-linux-gnueabihf") HOST = Some("armv7-unknown-linux-gnueabihf") CC_armv7-unknown-linux-gnueabihf = None CC_armv7_unknown_linux_gnueabihf = Some("/usr/bin/gcc") CFLAGS_armv7-unknown-linux-gnueabihf = None CFLAGS_armv7_unknown_linux_gnueabihf = Some("-std=gnu99 -I/builddir/build/BUILD/firefox-87.0/objdir/dist/system_wrappers -include /builddir/build/BUILD/firefox-87.0/config/gcc_hidden.h -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fstack-
Is this with LTO enabled?
I suspect it's the same issue we see in our CI on all other platforms as well. After an update to the swgl component by FF upstream it requires an excessive amount of memory (and time too) for the rust -> g++ -> gas process tree (on ppc64le cc1plus tops at 8GB, gas needs additional 5GB).
(In reply to Peter Robinson from comment #1) > Is this with LTO enabled? We build with PGO+LTO on Intel only.
I don't have a proof, but it looks to me that the excessive amount of memory isn't required for builds of trunk any more.
This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle. Changing version to 35.
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.