Bug 852203

Summary: gfortran gives a ICE error for virtually all fortran code on calxeda machine
Product: [Fedora] Fedora Reporter: William Cohen <wcohen>
Component: gccAssignee: Jakub Jelinek <jakub>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: dmarlin, jakub, law
Target Milestone: ---   
Target Release: ---   
Hardware: arm   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-28 22:32:24 UTC Type: Bug
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
file to reproduce the problem none

Description William Cohen 2012-08-27 20:43:57 UTC 
Created attachment 607345 [details]
file to reproduce the problem

Description of problem:

On calxeda arm machine with fedora 17 installed can't compile any fortran code. Always getting the following error for any code:

 
<built-in>:0:0: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://bugzilla.redhat.com/bugzilla> for instructions.


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

kernel-highbank-3.5.2-3.fc17.armv7hl
gcc-gfortran-4.7.0-5.fc17.armv7hl
mpfr-3.1.0-2.fc17.armv7hl


How reproducible:

Every time


Steps to Reproduce:
1. Install the gcc-gfortran on calxeda machine
2.  gfortran  hello.F
3.
  
Actual results:

# gfortran  hello.F
<built-in>:0:0: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://bugzilla.redhat.com/bugzilla> for instructions.


Expected results:

A runnable a.out file.


Additional info:

The gfortran compiler seems to work fine on a similar trimslice machine running fedora 17. Not sure if this is some wacky set up problem with the calxeda machine.  The calxeda machine has 4GB of memory compared to the <=1GB on the trimslice.

One thing notice that is difference in the "gfortran --verbose hello.F" output between the calxeda and trimslice are the GCC heuristics. On calxeda machine:

GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072

On trimslice:

GGC heuristics: --param ggc-min-expand=89 --param ggc-min-heapsize=112300
Comment 1 D. Marlin 2012-08-28 14:50:42 UTC 
The sample program builds and runs without errors for me on a Calxada Highbank system running versions:

  kernel-highbank-3.4.6-2.fc17.armv7hl
  gcc-gfortran-4.7.0-5.fc17.armv7hl
  mpfr-3.1.0-2.fc17.armv7hl
  glibc-2.15-37.fc17.armv7hl


[root@highbank-1-f17-v7hl ~]# gfortran hello.F
[root@highbank-1-f17-v7hl ~]# ./a.out
 Hello World!


[root@highbank-1-f17-v7hl ~]# head -n1 /proc/meminfo 
MemTotal:        4138020 kB


GNU Fortran (GCC) version 4.7.0 20120507 (Red Hat 4.7.0-5) (armv7hl-redhat-linux-gnueabi)
   compiled by GNU C version 4.7.0 20120507 (Red Hat 4.7.0-5), GMP version 5.0.2, MPFR version 3.1.0, MPC version 0.9

GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
Comment 2 William Cohen 2012-08-28 22:32:24 UTC 
There seems to be a problem with the way that the software was installed on the machine.  Did the following to reinstall the rpms:

rpm -qa |sort > /tmp/wonky_rpm.log
yum reinstall `cat /tmp/wonky_rpm.log`


That seemed to resolve the problem