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: Add uninitialized attribute?

From: Diego Novillo <dnovillo at google dot com>
To: "H.J. Lu" <hjl dot tools at gmail dot com>
Cc: GCC Development <gcc at gcc dot gnu dot org>, "Kreitzer, David L" <david dot l dot kreitzer at intel dot com>, "Girkar, Milind" <milind dot girkar at intel dot com>
Date: Fri, 20 Aug 2010 15:52:45 -0400
Subject: Re: Add uninitialized attribute?
References: <AANLkTikiQ3dRQuNjCNHKQk+QQ4pPYj14V-A5Brb0fan7@mail.gmail.com>

On 10-08-20 15:42 , H.J. Lu wrote:

Hi,

Sometime I have to do

int x = 0;
to silence gcc from uninitialized warnings when I know it is
unnecessary.  Is that a good idea to add
int x __attribute__ ((uninitialized));

to tell compiler that it is OK for "x" to be uninitialized?

Seems to me that there is a lot less typing with the '= 0' variant.

However, there have been several instances (particularly in C++) where providing an initial value is somewhat more convoluted.

Diego.

References:
- Add uninitialized attribute?
  - From: H.J. Lu

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