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: 'xxx' may be used uninitialized in this function

From: Daniel Jacobowitz <drow at false dot org>
To: Bruce Korb <bkorb at gnu dot org>
Cc: gcc at gcc dot gnu dot org
Date: Wed, 9 Aug 2006 16:12:34 -0400
Subject: Re: 'xxx' may be used uninitialized in this function
References: <668c430c0608090835p24125b36t1a9f1e6fbcdb6340@mail.gmail.com> <20060809160354.GA25555@nevyn.them.org> <668c430c0608090909oa86d0fdq2a5b0cf85209ec94@mail.gmail.com>

On Wed, Aug 09, 2006 at 09:09:56AM -0700, Bruce Korb wrote:
> Here is the real code.  The complaint is about pOptTitle.
> The compiler is GCC 4.1.1.  Both "set*OptFmts" functions
> *WILL* set pOptTitle to something.  Option level is -O4, so
> flow analysis is being done:

As you probably know by now, one can't look at a bug of this sort
without a compilable test case.  Andrew correctly pointed out that this
optimization is affected by (for instance) inlining.

-- 
Daniel Jacobowitz
CodeSourcery

Follow-Ups:
- Re: 'xxx' may be used uninitialized in this function
  - From: Bruce Korb

References:
- 'xxx' may be used uninitialized in this function
  - From: Bruce Korb
- Re: 'xxx' may be used uninitialized in this function
  - From: Daniel Jacobowitz
- Re: 'xxx' may be used uninitialized in this function
  - From: Bruce Korb

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