Re:Writing C software without the standard library
by time4tea on Wednesday November 30, 2016 @01:28PM
(#13073264)
Well, not if you expect that you will have exactly the same time/space behaviour and pre/post conditions.
This is why lots of embedded, secure and defense software doesn't use standard libraries, and printf will instead be called sio04583 or something....
Also.. Don't forget that you can get gcc to get rid of unused code when compiling static executables, and use sstrip (yes, two 's' - it's a different program) to strip even more, if it's an ELF binary...
Re:Writing C software without the standard library
by sqeaky on Tuesday November 29, 2016 @01:33PM
(#13065088)
Depending on the scope of your project porting libc itself might be good idea. Then you simplify porting any tools you need that also use libc. Then you can port a few extra dependencies, then more tools...
Of course, if your target archs are all supported by libc, porting is much easier with libc.