public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Tim Prince <tprince@computer.org> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/5914: Infinite loop when compiling with optimisation on of z_log.c of libf2c Date: Mon, 11 Mar 2002 13:16:00 -0000 [thread overview] Message-ID: <20020311211603.5278.qmail@sources.redhat.com> (raw) The following reply was made to PR c/5914; it has been noted by GNATS. From: Tim Prince <tprince@computer.org> 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
next reply other threads:[~2002-03-11 21:16 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-11 13:16 Tim Prince [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-03-16 7:56 toon 2002-03-13 14:06 Toon Moene 2002-03-12 21:06 Ulrich Jakobus 2002-03-12 13:06 Toon Moene 2002-03-11 21:16 Ulrich Jakobus 2002-03-11 13:59 toon 2002-03-11 7:56 jakobus
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20020311211603.5278.qmail@sources.redhat.com \ --to=tprince@computer.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).