From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16173 invoked by alias); 29 Oct 2003 17:40:49 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 16164 invoked by uid 48); 29 Oct 2003 17:40:48 -0000 Date: Wed, 29 Oct 2003 17:42:00 -0000 From: "chlunde+bug at ifi dot uio dot no" To: gcc-bugs@gcc.gnu.org Message-ID: <20031029174045.12828.chlunde+bug@ifi.uio.no> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug c++/12828] New: -floop-optimize is unstable on PowerPC X-Bugzilla-Reason: CC X-SW-Source: 2003-10/txt/msg02605.txt.bz2 List-Id: 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