https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109814
Arsen Arsenović <arsen at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |arsen at gcc dot gnu.org
--- Comment #7 from Arsen Arsenović <arsen at gcc dot gnu.org> ---
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.
luckily, -ffreestanding doesn't do much, so it might be the case that you can
just drop it.
I'm currently in the process of getting together a toolchain I can test this
on.
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?
