@whitequark @ireneista @nil I'm honestly kind of confused why nostdlib and freestanding are separate switches
Top-level
@whitequark @ireneista @nil I'm honestly kind of confused why nostdlib and freestanding are separate switches 4 comments
@lisyarus @eniko @whitequark @ireneista @nil Is there a reason you wouldn't want them synched up to be the same either way? @eniko @whitequark @ireneista @nil I think freestanding is "there is no memcpy" and nostdlib is "I brought my own memcpy" so you'd use one for your memcpy and friends and the other for the rest of your very custom system? |
@eniko @whitequark @ireneista @nil Afaik freestanding is an option for the compiler itself while nostdlib is effectively an option for the linker (or rather to control the linker inputs), maybe that's the reason they're separate