On Fri, 8 Jun 2018 at 19:58, Zachary Turner <ztur...@google.com> wrote: > > > > On Fri, Jun 8, 2018 at 11:52 AM Pavel Labath <lab...@google.com> wrote: >> >> On Fri, 8 Jun 2018 at 18:48, Leonard Mosescu <mose...@google.com> wrote: >> > >> > To me, a linker order file (of any linker) sounds like a good >> abstraction level for generating that kind of input (on linux, I might >> have preferred a .s file with hardcoded .loc directives, but that >> doesn't seem to be a thing on windows). > > > Why not? I think that would work fine (it’s called .cv_loc in codeview > though)
Because I didn't know that's possible? :D I dropped a remark about .s files several pages back but noone picked it up, so I assumed it's infeasible for some reason. If that is the case, then this really sounds like a good idea. This way we should be even able to generate the split function without relying on PGO or checked-in binaries. _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits