public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	thorpej@shagadelic.org
Subject: Re: optimization/8492: [3.3 regression] GCC spins forever compiling loop
Date: Mon, 25 Nov 2002 07:56:00 -0000	[thread overview]
Message-ID: <20021119012939.24588.qmail@sources.redhat.com> (raw)

Old Synopsis: GCC spins forever compiling loop
New Synopsis: [3.3 regression] GCC spins forever compiling loop

State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Mon Nov 18 17:29:37 2002
State-Changed-Why:
    Confirmed. Compiles fine with 2.95 and 3.2.1, but hangs
    with 3.3 of today. Code is this:
    ---------------------------------
    int count;
    
    int func(int *valp) {
      int val, locked = 0;
    
      while ((val = *valp) != 0) {
        if (count) {
          if (count)
            locked = 1;
          else
            locked = 1;
    
          if (!locked)
            continue;
        }
    
        if (!count)
          count--;
    
        break;
      }
    
      return val;
    }
    ----------------------------

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8492


             reply	other threads:[~2002-11-19  1:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-25  7:56 bangerth [this message]
2002-12-20 14:56 Janis Johnson
2002-12-21  3:16 Jan Hubicka
2002-12-21  3:16 Eric Botcazou
2002-12-21  4:46 Eric Botcazou
2002-12-21 15:46 Jan Hubicka
2003-01-14 20:07 ebotcazou

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=20021119012939.24588.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=thorpej@shagadelic.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: link
Be 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).