jasonmolenda wrote: I know your benchmarking numbers are against the `main` swiftlang branch which is using stable/20230725 - it's a bit older than llvm-project main as you'd guess from the date. They're bringing up the `rebranch` branch right now to become `main` at some point (I haven't followed closely enough to know when) and that's a fork of main from stable/20240723, a bit closer to `main` and it is possible there have been other changes that have an impact on perf. I'll see if I can't build up `rebranch` and see how that behaves, but as far as github main goes, it's clearly a wallclock improvement for macOS apps.
The other thing we may want to consider (you don't need to take this on in your current work) is the module creation in `Target::SetExecutableModule` - this happens when you run `lldb MyBinary.app` - it will create Modules for MyBinary plus all libraries it links to, and all libraries they link to, etc, before it has run or executed anything. For a Simulator app , Xcode requests the app launch and then tells lldb to attach to the pid, so I don't think lldb is given the binary before that and this is not important. But it will be relevant for other workflows. https://github.com/llvm/llvm-project/pull/110439 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
