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]

Re: Uninitialized variable warnings

To: zack at rabi dot columbia dot edu (Zack Weinberg)
Subject: Re: Uninitialized variable warnings
From: Joern Rennecke <amylaar at cygnus dot co dot uk>
Date: Tue, 16 Mar 1999 19:57:47 +0000 (GMT)
Cc: egcs at egcs dot cygnus dot com

> I didn't know that either.  Is there a difference between
> (reg_equiv_mem[i] || reg_equiv_address[i]) and
> reg_equiv_memory_loc[i]?  If not, why is there a separate table?

reg_equiv_memory_loc gets set first.  later reload decides if to set
reg_equiv_mem or reg_equiv_address.

>         else if (GET_CODE (value.base) == LABEL_REF)
...
> If GET_CODE (value.base) is not SYMBOL_REF or LABEL_REF, hi is used
> unintialized.  Maybe that never happens with correct RTL, but we ought

Oops, I missed the 'if' in the 'else if',

References:
- Re: Uninitialized variable warnings
  - From: Zack Weinberg

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