This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: target/5353: GCC/arm runs forever with -O on this file (mhz.c from lmbench)
- From: Philip Blundell <pb at nexus dot co dot uk>
- To: nobody at gcc dot gnu dot org
- Cc: gcc-prs at gcc dot gnu dot org,
- Date: 10 Jan 2002 22:56:00 -0000
- Subject: Re: target/5353: GCC/arm runs forever with -O on this file (mhz.c from lmbench)
- Reply-to: Philip Blundell <pb at nexus dot co dot uk>
The following reply was made to PR target/5353; it has been noted by GNATS.
From: Philip Blundell <pb@nexus.co.uk>
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.