Bug 78548 - g77 -c -O3 -g stl.f : Internal compiler error in add_abstract_origin_attribute
g77 -c -O3 -g stl.f : Internal compiler error in add_abstract_origin_attribute
Product: Red Hat Linux
Classification: Retired
Component: gcc (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jakub Jelinek
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2002-11-25 11:36 EST by Peter Dalgaard
Modified: 2007-04-18 12:48 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-10-01 16:49:32 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Source code for offending function (15.22 KB, text/plain)
2002-11-25 11:38 EST, Peter Dalgaard
no flags Details

  None (edit)
Description Peter Dalgaard 2002-11-25 11:36:06 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020607

Description of problem:
g77 compiler error triggered by -c -g -O3 combination on this file.
Removing -g or reducing -O level clears problem. A file cut qdown to just the
stlez routine removes the error.

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

How reproducible:

Steps to Reproduce:
1.g77 -c -O3 -g stl.f

Actual Results:  stl.f: In subroutine `stlez':
stl.f:477: Internal compiler error in add_abstract_origin_attribute, at
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://bugzilla.redhat.com/bugzilla/> for instructions.

Expected Results:  normal compile of stl.o 

Additional info:

Offending file is on my website. See URL above. 

$ rpm -qf `which g77`
Comment 1 Peter Dalgaard 2002-11-25 11:38:25 EST
Created attachment 86346 [details]
Source code for offending function
Comment 2 Vladimir Makarov 2004-10-01 16:49:32 EDT
I've checked the current state of redhat gcc3.2 branch
(gcc-3_2-rhl8-branch).  The bug was gone.  Therefore we are closing
the case.

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