[llvm-dev] A libc in LLVM
Ben Craig via llvm-dev
llvm-dev at lists.llvm.org
Mon Jul 15 12:25:09 PDT 2019
Note that libc++abi (i.e. the thing that implements much of the C++ runtime) is implemented with a subset of C++. It is possible to use a subset of C++ without pulling in a dynamic runtime.
> -----Original Message-----
> From: llvm-dev <llvm-dev-bounces at lists.llvm.org> On Behalf Of David
> Greene via llvm-dev
> Sent: Monday, July 15, 2019 2:02 PM
> To: David Jones <dlj at google.com>
> Cc: Aaron Ballman via llvm-dev <llvm-dev at lists.llvm.org>; Marshall Clow
> <mclow.lists at gmail.com>
> Subject: [EXTERNAL] Re: [llvm-dev] A libc in LLVM
>
> David Jones <dlj at google.com> writes:
>
> > >> * Provide C symbols as specified by the standards, but take
> > advantage >> and use C++ language facilities for the core implementation.
> >
> > Does this mean C programs would require a C++ runtime? If not, how
> > will the project ensure that?
> >
> > Shooting from the hip: no. Turning off exceptions, RTTI, and static
> > initializers (i.e., things which require a guard variable) is probably
> > enough to obviate the need for the runtime.
>
> What about bits of the standard library that are not header-only? My guess
> is that the set of those things may be platform-dependent.
>
> -David
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://urldefense.com/v3/__https://lists.llvm.org/cgi-
> bin/mailman/listinfo/llvm-
> dev__;!fqWJcnlTkjM!4ub_gnh6OCD9cC5QP1PCRvBBd5QktHyTY8u78311YmZ
> OnA0Pe8bkXsyPvAai$
More information about the llvm-dev
mailing list