• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: cc1obj: warning: -Wuninitialized is not supported without -O <--- huh?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: cc1obj: warning: -Wuninitialized is not supported without -O <--- huh?


  • Subject: Re: cc1obj: warning: -Wuninitialized is not supported without -O <--- huh?
  • From: Nick Zitzmann <email@hidden>
  • Date: Thu, 21 Jul 2005 09:47:10 -0600


On Jul 21, 2005, at 09:41 AM, Frederick C. Lee wrote:

cc1obj: warning: -Wuninitialized is not supported without -O

The sample code was written by an Apple staffer in 2004 and contains some deprecated code (in Tiger's eyes).

What does this warning mean, and how do I correct it?

It means that the -Winitialized GCC flag, which turns on the "variable might be used uninitialized" warnings, doesn't work unless optimization is turned on (the -O option). You should probably turn that warning off in the target settings for debug builds or other builds with zero optimization.


Nick Zitzmann
<http://www.chronosnet.com/>


_______________________________________________ Do not post admin requests to the list. They will be ignored. Cocoa-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >cc1obj: warning: -Wuninitialized is not supported without -O <--- huh? (From: "Frederick C. Lee" <email@hidden>)

  • Prev by Date: Re: Catching system signals and exception handling
  • Next by Date: Compositing an NSImage on top of an NSView subclass
  • Previous by thread: cc1obj: warning: -Wuninitialized is not supported without -O <--- huh?
  • Next by thread: Compositing an NSImage on top of an NSView subclass
  • Index(es):
    • Date
    • Thread