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

Link-time optimization and static libraries


  • Subject: Link-time optimization and static libraries
  • From: Jens Alfke <email@hidden>
  • Date: Wed, 09 Dec 2015 17:09:20 -0800

I’d like to try out link-time optimization in my project, but that project is a framework, which on iOS is built as a static library. I assumed the LTO option wouldn't affect building the library since there is no real link phase, so instead I enabled it in a separate target that builds an app that uses the library. I haven’t seen any speed improvements, though.

Now I’m wondering if LTO also affects the initial code generation, or maybe the metadata in the .o files. Does it need to be enabled for all targets that contribute code (.o files) to the binary being linked?

(I can’t find any good docs on this feature, btw. Xcode’s doc browser turns up nothing at all. Google finds a WWDC 13 talk and some low-level info about LLVM, but nothing useful.)

—Jens
 _______________________________________________
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


  • Follow-Ups:
    • Re: Link-time optimization and static libraries
      • From: Jens Alfke <email@hidden>
  • Prev by Date: Re: Can't get docsets
  • Next by Date: Re: Link-time optimization and static libraries
  • Previous by thread: Re: Can't get docsets
  • Next by thread: Re: Link-time optimization and static libraries
  • Index(es):
    • Date
    • Thread