From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21321 invoked by alias); 10 Jan 2002 22:56:00 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 21305 invoked by uid 71); 10 Jan 2002 22:56:00 -0000 Date: Thu, 10 Jan 2002 14:56:00 -0000 Message-ID: <20020110225600.21304.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Philip Blundell Subject: Re: target/5353: GCC/arm runs forever with -O on this file (mhz.c from lmbench) Reply-To: Philip Blundell X-SW-Source: 2002-01/txt/msg00419.txt.bz2 List-Id: The following reply was made to PR target/5353; it has been noted by GNATS. From: Philip Blundell To: bjh21@netbsd.org Cc: gcc-gnats@gcc.gnu.org Subject: Re: target/5353: GCC/arm runs forever with -O on this file (mhz.c from lmbench) Date: Thu, 10 Jan 2002 22:53:19 +0000 >When compiling the attached code with -O, GCC (configured as above) seems to >run forever, eating CPU but not leaking memory. The command line (run from >within the GCC source tree) was: > >./xgcc -da -B. -O -v ~/mhz.i > >The -da produces dumps up to mhz.i.30.mach. A workaround is to compile >without -O. This bug has been present since at least egcs 1.1.2. Yes, this is something of an old favourite. I'm surprised it isn't in GNATS already. See, for example: http://gcc.gnu.org/ml/gcc-bugs/1999-09/msg00321.html p.