Description of problem: The latest build of mscore is taking a very long time on i386: https://koji.fedoraproject.org/koji/taskinfo?taskID=41620569. I can reproduce this in mock. After the build has been going for a short time, compilation slows to a crawl. By repeatedly running "ps", I have been able to observe that c++ has spawned a /usr/bin/as process, and that process is the one taking a very long time to complete on file after file. This is new behavior from the last mscore build, which used binutils 2.33.1. Version-Release number of selected component (if applicable): binutils-2.34-2.fc33 How reproducible: Always Steps to Reproduce: 1. fedpkg clone mscore 2. cd mscore 3. fedpkg srpm mscore 4. mock -r fedora-rawhide-i386 --rebuild mscore-3.4.2-1.fc33.src.rpm Actual results: The build becomes bogged down eventually, usually in the 70% to 80% done range. Running "ps" shows "/usr/bin/as" processes that take a very long time to complete. This does not happen on the other Fedora architectures. Expected results: Instantaneous builds. Sadly, I am always disappointed in this expectation. Where's the CPU with an infinite clock rate when you need one? Additional info:
(In reply to Jerry James from comment #0) > 4. mock -r fedora-rawhide-i386 --rebuild mscore-3.4.2-1.fc33.src.rpm This fails for me with: error: Bad exit status from /var/tmp/rpm-tmp.YSFtMA (%prep) RPM build errors: This package uses obsolete macros that will go away soon. Please convert to the spec templates provided by fonts-rpm-templates! By any chance are you able to capture the assembler source file that is taking so long to assemble ? That would save me a lot of time, and mean that I can experiment on it without needing to use mock. > Where's the CPU with an infinite clock rate when you need one? That's next on my todo list. Honest...
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle. Changing version to 33.
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. 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 Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days