Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 21198

Summary: gcc 2.96-64 has problems compiling LAPACK on SPARC
Product: [Retired] Red Hat Raw Hide Reporter: Trond Eivind Glomsrxd <teg>
Component: gccAssignee: Jakub Jelinek <jakub>
Status: CLOSED RAWHIDE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.0CC: rgorosito
Target Milestone: ---   
Target Release: ---   
Hardware: sparc   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-11-22 17:39:19 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:
Attachments:
Description Flags
FORTRAN file which triggers a problem in gcc. none

Description Trond Eivind Glomsrxd 2000-11-21 20:18:22 UTC 
gcc 2.96-64 has problems compiling claswp.f on SPARC with -O2 (-O1 works fine):

[root@bart /]# g77 -c -O1 claswp.f
[root@bart /]# g77 -c -O2 claswp.f
claswp.f: In subroutine `claswp':
claswp.f:116: Internal compiler error in verify_local_live_at_start, at
flow.c:2729
Please submit a full bug report.
See <URL:http://bugzilla.redhat.com/bugzilla/> for instructions.
[root@bart /]#

claswp.f is part of LAPACK.
Comment 1 Trond Eivind Glomsrxd 2000-11-21 20:19:05 UTC 
Created attachment 5626 [details]
FORTRAN file which triggers a problem in gcc.
Comment 2 Bill Nottingham 2000-11-22 05:09:12 UTC 
FWIW, when I ran an ia64 compiler on a buggy machine, it
*always* ICEd at that exact point. Maybe our sparcs have the
same hardware bug? :)
Comment 3 Jakub Jelinek 2000-11-22 17:39:15 UTC 
No, I'm able to reproduce it on my SPARC and even in an ia32->SPARC cross
g77. It does not happen in current CVS nor on subreg-byte branch (cut
in September), so I'll have to track down which patch fixes this.
Comment 4 Jakub Jelinek 2001-11-28 12:57:52 UTC 
This was fixed in gcc-2.96-101.