Bug 532763
| Summary: | qmc2 compilation takes eternity | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Julian Sikorski <belegdol> |
| Component: | gcc | Assignee: | Jakub Jelinek <jakub> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 12 | CC: | jakub, rdieter, tgl |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-02-11 16:50:27 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
Julian Sikorski
2009-11-03 18:17:38 UTC
Testcase added to http://gcc.gnu.org/PR41371, Alex Oliva will hopefully have a look soon. Short term workaround is to compile with -fno-var-tracking-assignments. This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping In case anyone is wondering, I can confirm that adding -fno-var-tracking-assignments to CXXFLAGS brings the compilation back to reasonable values - it took 8 minutes and 28 seconds this time. I have found that -fvar-tracking-assignments breaks mysql on s390: it's not a matter of compilation time, it's that the resulting executable fails its regression tests unless I add -fno-var-tracking-assignments. Is this likely to be the same issue described here, or should I file a new bug? (Unfortunately I do not have a good test case to submit, because I haven't localized the bug at all.) That's certainly unrelated, so please do file a new bug. gcc shouldn't generate different code between -fvar-tracking-assignments and -fno-var-tracking-assignments (not even between -g and -g0), any such case is considered a bug, so you could just strip -fvar-tracking-assignments and -fno-var-tracking-assignments generated object files and compare them, those that differ should be reported with preprocessed source and all gcc command line options. Oh, scratch that ... further experimentation shows that the same test sometimes passes and sometimes doesn't with identical compilation options. So the use of -fno-var-tracking-assignments probably didn't have anything to do with it. Sorry for the noise. Sorry for the late reply, but this needinfo has completely escaped my attention. Anyway, the results are as follows. Building qmc2-0.2-0.17.b13.fc12.src.rpm on this machine takes: - 10 min. 3 s; when using gcc-4.4.2-20 and -fno-var-tracking-assignments - 30 min. 23 s; when using gcc-4.4.2-24 w/o -fno-var-tracking-assignments In both of these cases the test was done in mock, with ccache and root_cache plugins disabled. RPMs for mock were all available locally, nothing had to be downloaded. Real-time build.log monitoring has revealed that the compiler needed most of the time to compile qrc_qmc2.cpp. gcc-4.4.2-4.fc12 errata has been released. |