On Wed, Sep 20, 2023 at 08:23:32AM -0400, Siddhesh Poyarekar wrote: > On 2023-09-20 07:58, Siddhesh Poyarekar wrote: > > On 2023-09-20 07:55, Jakub Jelinek wrote: > > > On Wed, Sep 20, 2023 at 07:50:43AM -0400, Siddhesh Poyarekar wrote: > > > > + Support libraries such as libiberty, libcc1 libvtv and libcpp have > > > > > > Missing comma before libvtv. But more importantly, libvtv is not > > > support library like libiberty, libcpp, it is more like the sanitizer > > > libraries runtime library for -fvtable-verify= . > > > > Ack, I'll move libvtv out. > > > > > And, libcc1 also isn't a compiler support library, but support library > > > for a GDB plugin. > > > > > > > Isn't that like libiberty then, which also gets used by other toolchain > > projects? Maybe calling it "Toolchain support libraries" would make it > > more explicit? > > I just noticed (ENOCOFFEE) that the line (after removing libvtv) is: > > Support libraries such as libiberty, libcc1 and libcpp have been > developed separately to share code with other tools such as binutils > and gdb. > > Does that address your concern Jakub?
I believe that is the case just for libiberty. libcpp is I think solely used by gcc itself (several frontends use it though, plus some build utilities in gcc). libcc1 is code for gdb with gcc implementation details. Jakub