Friday, May 6, 2016 [Tweets] [Favorites]

A Tale of Two Optimizers

Daniel Jalkut:

Today, Apple got back to me with a followup, suggesting rather gently that I may have neglected to disable optimization in my target. Rookie move! The kind of behavior I was seeing in the debugger is exactly what happens when lldb can’t make as much sense of your code because of inlined functions, loops that have been restructured, etc.

In fact, I had correlated the symptoms with such a problem, but when I went to check on the status of my optimization settings, everything looked fine.

[…]

So why does debugging Swift fail so hard for me? Because Swift doesn’t use that optimization setting.

It uses SWIFT_OPTIMIZATION_LEVEL instead of GCC_OPTIMIZATION_LEVEL.

Comments

Stay up-to-date by subscribing to the Comments RSS Feed for this post.

Leave a Comment