[llvm-dev] A libc in LLVM
Zachary Turner via llvm-dev
llvm-dev at lists.llvm.org
Mon Jun 24 17:41:30 PDT 2019
I’m not totally sold on the idea of having it be a layer between system
libc and application. I think this is likely to create a split between
windows and non windows that will be difficult to overcome.
It also seems like it brings with it its own set of difficulties. Where
can you make a separation in libc such that you’re guaranteed that the two
pieces do not share any state, especially given that not everyone is going
to be using the same libc?
Have you considered just starting with a blank slate?
On Mon, Jun 24, 2019 at 5:33 PM Chris Lattner via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> <disclaimer: I work at Google, though not on anything related to this
> On Jun 24, 2019, at 3:23 PM, Siva Chandra via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
> We are still in the early stages, but we do have some high-level goals and
> guiding principles of the initial scope we are interested in pursuing:
> 1. The project should mesh with the "as a library" philosophy of the
> LLVM project: even though "the C Standard Library" is nominally "a
> library," most implementations are, in practice, quite monolithic.
> This is awesome. I’d really love to see a corpus of functionality built
> as a set of libraries that can be sliced and remixed in different ways per
> the needs of different use-cases.
> For these areas, the community is of course free to contribute. Our hope
> is that, preserving the "as a library" design philosophy will make such
> extensions easy, and allow retaining the simplicity when these features
> aren't needed.
> We intend to build the new libc in a gradual manner. To begin with, the
> new libc will be a layer sitting between the application and the system
> libc. Eventually, when the implementation is sufficiently complete, it will
> be able to replace the system libc at least for some use cases and contexts.
> So, what do you think about incorporating this new libc under the LLVM
> I would love to see this, and I think it would fill a significant missing
> piece in the LLVM ecosystem.
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-dev