RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 972876 - c++ compiler becomes non-functional when source >65K
Summary: c++ compiler becomes non-functional when source >65K
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: gcc
Version: 6.3
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Jakub Jelinek
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-10 17:40 UTC by David Comeau
Modified: 2016-10-08 11:58 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-04 18:47:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description David Comeau 2013-06-10 17:40:18 UTC
Description of problem:I started writing an application, and when the source code got to about 65K in size, the compiler went into paralisys.  I can make a change to the code.  Gedit will confirm the change.  I execute the build, and it runs error free.  The Make is run without any nagative indications.  When the code is executed, nothing has changed.
    I am prepared to submitt as much code and data examples as requested.
Is there a compiler option I can use to invoke a large program? 

Version-Release number of selected component (if applicable):


How reproducible:I wrote a Dump.cpp program, it works without errors, and the data presentation is faithful.


Steps to Reproduce:
1.I can ship the source code and the data field if requested.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 David Comeau 2013-06-11 12:39:08 UTC
Following Data obtained in System Terminal Mode:

gcc --version
System Version: gcc (GCC) 4.4.6  20120305 (Red Hat 4.4.6-4)

make --version
Make: GNU Make 3.81
"This program built for x86_64-redhet-linux-gnu"

Ststem: Red Hat Enterprise Linux Server
Release 6.3 (Santiago)
Kernel Linux 2.6.32-279.el6.x86_64
Memory: 15.2 GiB
Processor 0: Intel(R)Core(TM) i5-2500K cpu @3.30 Ghz (Same for Proc 1,2,3)
System Status: 417.4 GiB

Comment 3 David Comeau 2013-07-09 17:00:21 UTC
refrence #982235

Comment 4 Jakub Jelinek 2013-07-18 22:14:33 UTC
Without a reproducer there is nothing to do.  What exactly does g++ do?  Consume lots of CPU time until you kill it, something else?  If you can, please preprocess it (e.g. add -save-temps), attach the preprocessed source here and mention the exact command line options used to compile it.

Comment 6 David Comeau 2016-10-08 11:58:54 UTC
OK to close this report.  Problem was either discovered and/or a work-around was found.

Thank you for your support.


Note You need to log in before you can comment on or make changes to this bug.