News for hackers. Stuff that matters.

A comment on C Runtime Overhead (2015). Parent comment

Re:C Runtime Overhead (2015) by justicezyx on Monday January 03, 2022 @05:40PM (#29788053)
But the 1ms number is also measured with strace.

Plus, the article is in 2015, and the author did not mention the CPU and other configuration. So that also make things muddy.

[ Parent | on HN ]
Re:C Runtime Overhead (2015) by cozzyd on Monday January 03, 2022 @05:42PM (#29788077)
Yes, but if there are almost no syscalls, then strace is doing a lot less.

Profiling my trivial program with callgrind shows (unsurprisingly) that the majority of the time is in dynamic library relocation and whatever __GI__tunables_init does: https://i.imgur.com/Yligh7S.png

[ Parent | on HN ]