search for: clangmr

...via a library call. >> >> Given that clang can fork, I assume that this new clang+lld can fork. >> > > No, it cannot in all cases. We have genuine use cases where forking isn't > realistically an option. As an example, imagine that you want to use > something like ClangMR (which I presented ages ago) but actually *link* > code massively at scale to do post-link analysis of the binaries? There are > environments where we need to be able to run the linker on multiple > different threads in a single address space and collect the linked object > in an in-mem...

> There are probably others, but this is the gist of it. Now, you could still > design everything with the simplest imaginable API, that is incredibly > narrow and specialized for a *single* user. But there are still fundamentals > of the style of code that are absolutely necessary to build a library. And > the only way to make sure we get this right, is to have the single user of

...iven that clang can fork, I assume that this new clang+lld can fork. >>>> >>> >>> No, it cannot in all cases. We have genuine use cases where forking >>> isn't realistically an option. As an example, imagine that you want to use >>> something like ClangMR (which I presented ages ago) but actually *link* >>> code massively at scale to do post-link analysis of the binaries? There are >>> environments where we need to be able to run the linker on multiple >>> different threads in a single address space and collect the linked...