News for hackers. Stuff that matters.
Re:What causes Ruby memory bloat? by jchw on Friday March 15, 2019 @01:57PM (#19402346)
- 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.)

Re:What causes Ruby memory bloat? by pjmlp on Friday March 15, 2019 @03:26PM (#19403280)
There is a world beyond gcc, clang and MSVC.

Just out of my head, MikroElektronika, TI, Green Hills, Embarcadero, IBM, HP, Unisys, Intel, PGI.

Re:What causes Ruby memory bloat? by jchw on Friday March 15, 2019 @04:29PM (#19403986)
Even then, the comments regarding "freestanding" C runtimes are the same. Targeting bare metal puts the standard library squarely out of scope of the standard.