This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug c++/12828] New: -floop-optimize is unstable on PowerPC


PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12828

           Summary: -floop-optimize is unstable on PowerPC
           Product: gcc
           Version: 3.3.2
            Status: UNCONFIRMED
          Severity: critical
          Priority: P2
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: chlunde+bug at ifi dot uio dot no
                CC: gcc-bugs at gcc dot gnu dot org
  GCC host triplet: powerpc-linux-gnu

Perfectly fine code seems to give segmentation faults on PowerPC with the new 
-floop-optimize flag.  I've only tested this with GCC 3.3.2 from Debian 
unstable. 
 
Here's a small example of code which gives SIGSEGV 
http://www.rashbox.org/~chlunde/gccloopbug.cc


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]