There is a major regression in gcc-4.2.0, which upstream has admitted to. They have put up a patch that I have updated with the modifications needed to prevent the ice when building fortran. Reproducible: Always Steps to Reproduce: 1. update gcc-4.2.0 2. emerge xorg-server 3. Actual Results: xorg-server uses all avaliable memory and swap, can take up to 8 hours to build on a decent system. Expected Results: regression should be fixed as it prevents testing.
Created attachment 120667 [details] gcc-4.2.0-x86_64-regression.patch All info on upstream bug. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30052
saying "a regression" is not trackable by any means
*** Bug 181157 has been marked as a duplicate of this bug. ***
*** Bug 182015 has been marked as a duplicate of this bug. ***
added the change that actually went into the branch: http://gcc.gnu.org/viewcvs?view=rev&revision=125227
(In reply to comment #5) > added the change that actually went into the branch: > http://gcc.gnu.org/viewcvs?view=rev&revision=125227 > It would be appreciated if a changelog was made that documents all changes instead of making users guess as to what has changed.
why dont you read the changelog in the patchset
*** Bug 191487 has been marked as a duplicate of this bug. ***
*** Bug 192799 has been marked as a duplicate of this bug. ***
(In reply to comment #7) > why dont you read the changelog in the patchset Why don't you just revbump the thing as you are supposed to do in the first place - instead of letting users hit this bug over and over again because you've just silently changed the ebuild to use a new patchset?
i dont revbump things that were not keyworded ... users who want to play with things that arent meant to be played with get to track things themselves
