This is the mail archive of the gcc-patches@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]

[tree-ssa] Unused variable warnings


> > On Fri, Oct 17, 2003 at 06:57:47PM +0200, Jan Hubicka wrote:
> > > Also can I ask about the status of your changes in tree-ssa?  (it looks
> > > like they are responsible for the new misscompilations I am seeing with
> > > unit-at-a-time enabled.  I will look into these in case you don't have
> > > something ready already)
> > 
> > It's looking generally good.  I'm sure there are bugs, but they're
> > not overwhelming.
> I actually was referring to Jeff's changes from this week, but OK, I
> will dig into the inlining issues I have.
> It seems to be that it is shame that we don't test SPEC with -O3
> that would probably catch the problems much easier.
> (I seem to be running into at least 3 different missoptimizations
> related to inlining, hope to have something more specific soon)
OK,
I have one problem.  It is a warning:
../../gcc/haifa-sched.c:2042: warning: 'index' might be used uninitialized in this function

index is initialized by:
if (max_issue (ready, &index) == 0)
 
where max_issue is function that really has path throught that really
does not write into the index variable, so this warning is de-facto
right, just not obvious.  What do we want to do here?
Shall I simply add initializer to this variable and another one in
f/lex.c as we do in usual case of this warning?

Honza


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