michaelrj-google wrote: Right now we don't really have a "freestanding" mode, we've got "baremetal" targets which are meant for systems without an OS but they have a lot more than just those four memory functions. You may be thinking of "fullbuild" vs "overlay", which determines if we provide our own libc headers or use the ones provided by the system's existing libc respectively. That's interesting, but seems orthogonal to this specific change.
Similar to jhuber, I'm curious about what freestanding means for the library. Is the expectation that a freestanding c library provide _just_ the four listed memory functions, or is it expected to provide a more complete runtime. I'm not sure how/why we'd provide startup code that initializes C++ variables but can't also call main. Also what's the linking expectations? Is it required to be fully static or is the libc expected to provide a loader? https://github.com/llvm/llvm-project/pull/132232 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
