The Tizen stack is rather large and there are many, many packages that depend on the full functionality of glibc. Using another libc is likely not to be an option at all, even if there was quantifiable evidence that 'the other' libc is somehow much faster (something I doubt). Size doesn't seem like an issue to me either; compared to the rest of the stack, glibc is just another building block. Have you stripped everything else away that is not needed on your system and now you're down to glibc as the issue?
Pete On Dec 11, 2012, at 8:20 AM, Rohit Pathania wrote: > Hi Gustavo, > Android can use bionic because it barely uses libc, adding all the java > slow crap. Can you please elaborate more on this line. > > Thanks & Regards, > Rohit Pathania > > On Tue, Dec 11, 2012 at 7:47 PM, Gustavo Sverzut Barbieri > <[email protected]> wrote: > c because it barely uses libc, adding all the java slow > crap. > > _______________________________________________ > General mailing list > [email protected] > https://lists.tizen.org/listinfo/general _______________________________________________ General mailing list [email protected] https://lists.tizen.org/listinfo/general
