Hide Forgot
Created attachment 551393 [details] Preprocessed source Description of problem: GCC 4.6.2 20111027 giving internal compiler error for C codes. Even for a simple hello world program. Version-Release number of selected component (if applicable): Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/4.6.2/lto-wrapper Target: x86_64-redhat-linux Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-gnu-unique-object --enable-linker-build-id --enable-languages=c,c++,objc,obj-c++,java,fortran,ada,go,lto --enable-plugin --enable-java-awt=gtk --disable-dssi --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre --enable-libgcj-multifile --enable-java-maintainer-mode --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --disable-libjava-multilib --with-ppl --with-cloog --with-tune=generic --with-arch_32=i686 --build=x86_64-redhat-linux Thread model: posix gcc version 4.6.2 20111027 (Red Hat 4.6.2-1) (GCC) How reproducible: Every time for any C code on current machine. Although its not a problem on a different machine running F16. Binary from other machine runs fine. Steps to Reproduce: 1. Compile any C on current F16 build. 2. 3. Actual results: hello.c: In function ‘main’: hello.c:6:3: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <http://bugzilla.redhat.com/bugzilla> for instructions. Preprocessed source stored into /tmp/cc4lYWKI.out file, please attach this to your bugreport. Expected results: Should compile fine. Additional info: Not sure of something in the installation. Here's a list of installed gcc rpms. rpm -qa | grep gcc gcc-gfortran-4.6.2-1.fc16.x86_64 gcc-4.6.2-1.fc16.x86_64 gcc-c++-4.6.2-1.fc16.x86_64 libgcc-4.6.2-1.fc16.x86_64
Not a gausssum bug. Refiling under gcc.
Thank you for your bug report. > How reproducible: > Every time for any C code on current machine. This may be a machine dependent problem ,setting severity to medium.Please attach stack trace , see http://fedoraproject.org/wiki/StackTraces for more information about getting a useful stack trace with debugging symbols. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I suggest trying to reinstall the GCC and base development packages and, if that doesn't solve the problem, run a memory checker on the machine.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.