This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: warning: '<some_var>' may be used uninitialized in this function

From: Joe Buck <Joe dot Buck at synopsys dot COM>
To: Daniel Berlin <dberlin at dberlin dot org>
Cc: Diego Novillo <dnovillo at redhat dot com>, Perry Smith <pedz at easesoftware dot net>, gcc at gcc dot gnu dot org, Christian dot Iseli at licr dot org
Date: Thu, 12 Jan 2006 11:24:46 -0800
Subject: Re: warning: '<some_var>' may be used uninitialized in this function
References: <200601121453.k0CErE1L021586@ludwig-alpha.unil.ch> <200601121001.55026.dnovillo@redhat.com> <857AE88A-71BF-4FDF-9737-C73C4CAC9CBD@easesoftware.net> <200601121024.27565.dnovillo@redhat.com> <Pine.LNX.4.63.0601121209240.11995@localhost.localdomain>

On Thu, Jan 12, 2006 at 12:13:06PM -0500, Daniel Berlin wrote:
> I hate to bring this up, because it's a "half-troll", but the halting 
> problem is *not* undecidable on the machines we use everyday, because they 
> have finite memory.

Fine.  Now you just have to come up with a solution before the heat death
of the universe.

Follow-Ups:
- Re: warning: '<some_var>' may be used uninitialized in this function
  - From: Daniel Berlin

References:
- warning: '<some_var>' may be used uninitialized in this function
  - From: Christian . Iseli
- Re: warning: '<some_var>' may be used uninitialized in this function
  - From: Diego Novillo
- Re: warning: '<some_var>' may be used uninitialized in this function
  - From: Perry Smith
- Re: warning: '<some_var>' may be used uninitialized in this function
  - From: Diego Novillo
- Re: warning: '<some_var>' may be used uninitialized in this function
  - From: Daniel Berlin

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]