From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5335 invoked by alias); 11 Mar 2002 21:16:08 -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 5285 invoked by uid 71); 11 Mar 2002 21:16:04 -0000 Date: Mon, 11 Mar 2002 13:16:00 -0000 Message-ID: <20020311211603.5278.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Tim Prince Subject: Re: c/5914: Infinite loop when compiling with optimisation on of z_log.c of libf2c Reply-To: Tim Prince X-SW-Source: 2002-03/txt/msg00350.txt.bz2 List-Id: The following reply was made to PR c/5914; it has been noted by GNATS. From: Tim Prince To: jakobus@emss.co.za, gcc-gnats@gcc.gnu.org Cc: Subject: Re: c/5914: Infinite loop when compiling with optimisation on of z_log.c of libf2c Date: Mon, 11 Mar 2002 13:10:26 -0800 On Monday 11 March 2002 07:46, jakobus@emss.co.za wrote: > >Number: 5914 > >Category: c > >Synopsis: Infinite loop when compiling with optimisation on of > > z_log.c of libf2c Confidential: no > >Severity: serious > >Priority: medium > >Responsible: unassigned > >State: open > >Class: wrong-code > >Submitter-Id: net > >Arrival-Date: Mon Mar 11 07:56:01 PST 2002 > >Closed-Date: > >Last-Modified: > >Originator: Ulrich Jakobus > >Release: 3.0.4 > >Organization: > >Environment: > > System: Linux uj-emss 2.2.16 #1 Wed Aug 2 20:22:26 GMT 2000 i686 unknown > Architecture: i686 > > > host: i686-pc-linux-gnu > build: i686-pc-linux-gnu > target: i686-pc-linux-gnu > configured with: ../gcc-3.0.4/configure > > >Description: > > Compiling the attached simple and short example file z_log.c (taken > from libf2c with specific input parameters) works fine for gcc-2.95.2 with > all levels of optimisation. For gcc-3.0.4 it also works for -O, but for -O2 > or higher we end up in an infinite loop. > > >How-To-Repeat: > > gcc -O2 z_log.c > > >Fix: > Didn't Toon Moene already work on this? Isn't this a loop at execution time? -- Tim Prince