We currently put everything in one single archive libc.a which breaks in
certain situations where the compiler drivers expect libm.a also. With
this change, we separate out libc.a and libm.a functions as is done
conventionally and put them in two different static archives.
One will now have to build two targets, libc and libm which produce
libc.a and libm.a respectively. Under default build, one still builds only
one target named libc which produces libllvmlibc.a.
Does this omit libm if there are no entrypoints for it enabled? Right now I haven't begun working on any libm related stuff.