[PATCH] D64939: Add a proposal for a libc project under the LLVM umbrella.

Aaron Ballman via llvm-commits llvm-commits at lists.llvm.org
Mon Aug 12 13:58:57 PDT 2019


On Mon, Aug 12, 2019 at 4:52 PM Siva Chandra <sivachandra at google.com> wrote:
>
> On Mon, Aug 12, 2019 at 1:00 PM Aaron Ballman <aaron at aaronballman.com> wrote:
> >
> > > dlj added inline comments.
> > >
> > > The specific mechanism, however, is something that ought to be addressed in a standalone design doc. We do have such a plan for ELF, but it is fairly intricate.
> >
> > Do you have similar plans for non-ELF systems?
>
> We do not currently have plans for non-ELF systems. [Others interested
> can of course come up with such mechanisms for non-ELF systems and
> contribute to the project.]

How should I interpret the statement the bullet point stating "Ability
to layer this libc over the system libc"? If this project does not
consider Windows support (e.g.) out of the box, I worry we will design
ourselves into unsupportable use cases. It's not that I want to commit
anyone to supporting other platforms right out of the box, but LLVM
supports non-ELF targets and so whatever we wind up with as a design
had better also support non-ELF targets and I'm not confident that's
the case here.

~Aaron


More information about the llvm-commits mailing list