News for hackers. Stuff that matters.
Re:The iPhone XS and XS Max Review: Unveiling the Silicon Se... by pertymcpert on Friday October 05, 2018 @11:46AM (#18149045)
Once the CPU reaches peak frequency the OS shouldn't be involved for CPU benchmarks. So it's more down to hardware.
Re:The iPhone XS and XS Max Review: Unveiling the Silicon Se... by ken on Friday October 05, 2018 @02:05PM (#18150308)
I can see how the compiler and stdlib (aren't things like memcpy implemented in hand-tuned assembly?) could be highly relevant, though.
Re:The iPhone XS and XS Max Review: Unveiling the Silicon Se... by pertymcpert on Friday October 05, 2018 @06:16PM (#18152181)
They are, but that’s really low hanging fruit. If Android for example doesn’t use optimised memcpy implementations then they don’t deserve to exist as a serious OS.
Re:The iPhone XS and XS Max Review: Unveiling the Silicon Se... by astrange on Saturday October 06, 2018 @08:17AM (#18154755)
That reminds me, when I read fast code in the 90s-2000s all the asm hackers were into writing their own cool memcpy. Were they just showing off, or did Windows actually never optimize their standard library?

People still seem to like writing their own cool malloc, but memcpy not so much.

Re:The iPhone XS and XS Max Review: Unveiling the Silicon Se... by pertymcpert on Wednesday October 10, 2018 @11:48AM (#18186005)
There are some cases where it may make sense to write your own implementation, if you have a niche microarchitecture that has unusual performance characteristics that the OS doesn't provide optimized routines for by default. But for most u-archs the default optimized routines should do a good job.

Things like malloc are quite a bit more complicated, and more workload dependent so there's still some opportunity specializing an implementation there.