Bug 732807

Summary: Heavy use of overloading causes g++ memory usage to skyrocket
Product: Red Hat Enterprise Linux 6 Reporter: Jakub Jelinek <jakub>
Component: gccAssignee: Jakub Jelinek <jakub>
Status: CLOSED ERRATA QA Contact: qe-baseos-tools-bugs
Severity: high Docs Contact:
Priority: high    
Version: 6.1CC: aravindvijayan224185, james.brown, jason, jwest, mbelangia, mpolacek, rtidwell
Target Milestone: rc   
Target Release: 6.2   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: gcc-4.4.6-3.el6 Doc Type: Bug Fix
Doc Text:
The C++ front-end used to consume lots of memory on codebases that used overloading heavily, with hundreds or more overloads of the same function or method. This lead to slow compile time that used lots of system resources. The front-end has been improved to use far less resources on such codebases.
Story Points: ---
Clone Of: 651098 Environment:
Last Closed: 2011-12-06 16:18:18 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:
Bug Depends On: 651098    
Bug Blocks:    

Comment 1 Jakub Jelinek 2011-08-24 16:14:13 UTC
Backported to 4.4-RH branch:
http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=178042

Comment 5 Jakub Jelinek 2011-11-28 13:44:15 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
The C++ front-end used to consume lots of memory on codebases that used overloading heavily, with hundreds or more overloads of the same function or method.  This lead to slow compile time that used lots of system resources.  The front-end has been improved to use far less resources on such codebases.

Comment 6 errata-xmlrpc 2011-12-06 16:18:18 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2011-1644.html