• 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: GC, variable optimized away wrongly?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GC, variable optimized away wrongly?


  • Subject: Re: GC, variable optimized away wrongly?
  • From: Shawn Erickson <email@hidden>
  • Date: Thu, 26 Nov 2009 07:20:38 -0800

On Wed, Nov 25, 2009 at 5:04 AM, Kyle Sluder <email@hidden> wrote:
> On Wed, Nov 25, 2009 at 4:50 AM, Nick Rogers <email@hidden> wrote:
>> Why is etaDouble is being optimized away?
>
> Because it is unused.

For those that may be wondering why etaDouble is optimized out but not
the lines above it as well despite those values not being used once
etaDouble is optimized out... well the compiler cannot optimize out
message sends because it cannot know the side effects of those
messages.

(Had this asked once by someone more used to C++ and inlined code)

-Shawn
_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >GC, variable optimized away wrongly? (From: Nick Rogers <email@hidden>)
 >Re: GC, variable optimized away wrongly? (From: Kyle Sluder <email@hidden>)

  • Prev by Date: NSDatePicker updates its values on changing System's time zone
  • Next by Date: Re: NSDatePicker updates its values on changing System's time zone
  • Previous by thread: Re: GC, variable optimized away wrongly?
  • Next by thread: Re: GC, variable optimized away wrongly?
  • Index(es):
    • Date
    • Thread