• 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: Link-time optimization and static libraries
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Link-time optimization and static libraries


  • Subject: Re: Link-time optimization and static libraries
  • From: Daniel Vollmer <email@hidden>
  • Date: Fri, 11 Dec 2015 00:25:41 +0100

Hi Jens,

> On the downside, it looks like LTO breaks some of the debug information: once I turned it on, when I stop at a breakpoint/crash in the app I can no longer see the source code of stack frames in the library code compiled with LTO; I just get disassembly. Is there a workaround for that?

I’m not sure about clang’s implementation, but when using LTO you may need to repeat what you may think of as compiler flags for the link step (like -g).

	Daniel.


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden


References: 
 >Link-time optimization and static libraries (From: Jens Alfke <email@hidden>)
 >Re: Link-time optimization and static libraries (From: Jens Alfke <email@hidden>)

  • Prev by Date: Xcode 7.2 / iOS 9.2 xcodebuild wrong architecture for simulator builds?
  • Next by Date: Can't po anything without getting tons of warnings
  • Previous by thread: Re: Link-time optimization and static libraries
  • Next by thread: Xcode 7.2 / iOS 9.2 xcodebuild wrong architecture for simulator builds?
  • Index(es):
    • Date
    • Thread