https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109814
--- Comment #8 from Andrew Pinski <pinskia at gcc dot gnu.org> --- (In reply to Arsen Arsenović from comment #7) > the thing with newlib in particular is that it's not really freestanding.. > it lives in an odd limbo between a full hosted OS and 'real' freestanding > with absolutely no (or minimal, e.g. libgcc and crti/n) runtime. > Right and a lot of people call newlib as being semi-hosted env. > I'm of the opinion it makes sense to treat newlib targets as hosted, even if > it isn't the fully featured OS library; what do you think? and what kind of > usecase are you working with? I am in the same opinion. I wonder how things like zephyr rtos are considered by themselves. They have their own libc which makes using libstdc++ a bit complex as almost always the libstdc++ is compiled for being with newlib ...
