News for hackers. Stuff that matters.
Re:Android Project Changeset 4f8b683: libc/memset.c by JoeAltmaier on Wednesday May 26, 2010 @08:26AM (#1380094)
Compilers have long ago memorized the code for memset (and memcopy and ...) and substitute optimized algorithms. As part of faking their benchmark stats for marketing purposes. So no worries, this code should result in kick-butt optimized assembler. Except for the obvious bug.
Re:Android Project Changeset 4f8b683: libc/memset.c by __david__ on Wednesday May 26, 2010 @03:44PM (#1381416)
Optimized for what? Speed? While I can picture that happening, it has been my experience that this is not the case. The memory squishing optimizations I'm talking about require dumping the assembly output and I've never seen my stupid memcpy() routine suddenly turn into optimized-for-speed code. I'd be pretty upset if that were to happen...