3 ms·
You didn't read the article, did you. Not to mention being spectacularly rude about it.
by pjc50 2y ago
You didn't read the article, did you. Not to mention being spectacularly rude about it.
- menaerus 2y agoNo, I actually read the article and I don't think I was spectacularly rude. I was rather just straight to the point. And rather than bitching "omg, why, oh why did a compiler turn a ctr into a function-call here?!" what I think I gave is a constructive suggestion how to fix the problem, if there was even one to begin with. What I see here in the article is pure theoreticizing and dwelling over details which in 99.9% of the cases do _not_ matter. There wasn't a single experiment shown by the author by which he shows that his use-case is in that 0.01%. I was basically done with reading the article when I read the following nonsense > accessing an extern thread_local with a constructor involves a function call, with the function testing the guard variable of the translation unit where the thread_local is defined. And then > But with inlining, the fast path is quite fast on a good processor. Right, the fast path of inlined ctr call vs slow path of non-inlined ctr call. Really? I call this a BS, especially without the experiments showing the data.