Subversion Repositories openrisc

/* m-un-1.c: "un" for "uninitialized" */

/* m-un-1.c: "un" for "uninitialized" */

/*

/*

From: Jim Wilson <wilson@cygnus.com>

From: Jim Wilson <wilson@cygnus.com>

Date: Wed, 6 Jul 1994 13:11:47 -0700

Date: Wed, 6 Jul 1994 13:11:47 -0700

To: dje@cygnus.com

To: dje@cygnus.com

Subject: Re: devo/gcc ChangeLog.fsf stmt.c

Subject: Re: devo/gcc ChangeLog.fsf stmt.c

Cc: cvs-gcc@cygnus.com, tege@cygnus.com

Cc: cvs-gcc@cygnus.com, tege@cygnus.com

        How about a test case?  :-)

        How about a test case?  :-)

Compile with -O -Wall and the broken compiler gives you:

Compile with -O -Wall and the broken compiler gives you:

tmp.c:6: warning: `k' might be used uninitialized in this function

tmp.c:6: warning: `k' might be used uninitialized in this function

The fixed compiler (and gcc 2.5.8) gives no warning.

The fixed compiler (and gcc 2.5.8) gives no warning.

This happens to fix a performance regression in the code generated for

This happens to fix a performance regression in the code generated for

while loops, but that is presumably much much harder to test for.

while loops, but that is presumably much much harder to test for.

*/

*/

/* { dg-do compile } */

/* { dg-do compile } */

/* { dg-options "-O -Wall" } */

/* { dg-options "-O -Wall" } */

int

int

sub ()

sub ()

{

{

  int i = 0;

  int i = 0;

  int j = 0;

  int j = 0;

  int k;        /* { dg-bogus "`k' might be used uninitialized" "uninitialized warning regression" } */

  int k;        /* { dg-bogus "`k' might be used uninitialized" "uninitialized warning regression" } */

  while (i == 0 && j == 0)

  while (i == 0 && j == 0)

    {

    {

      k = 10;

      k = 10;

      i = sub ();

      i = sub ();

    }

    }

  return k;

  return k;

}

}