Re:What causes Ruby memory bloat?
by pjmlp on Friday March 15, 2019 @01:29PM
(#19402006)
Because not every OS is an UNIX clone and C also targets bare metal.
[ Parent
| on HN ]
- afaik freestanding C specifies no standard library at all (except pure headers,) so bare metal targets providing libc are going beyond the standard.
- I'm just saying it doesn't need to specify who implements the standard library. I've read the standard before and I don't really recall this coming up, I'm just assuming this assertion is accurate.
(And of course, the overwhelming reality is that libc is provided by none of the compilers except Microsoft C, since Clang and GCC tend to be used with glibc.)
There is a world beyond gcc, clang and MSVC.
Just out of my head, MikroElektronika, TI, Green Hills, Embarcadero, IBM, HP, Unisys, Intel, PGI.