this post was submitted on 22 Apr 2024
15 points (94.1% liked)

C++

1695 readers
9 users here now

The center for all discussion and news regarding C++.

Rules

founded 1 year ago
MODERATORS
top 4 comments
sorted by: hot top controversial new old
[–] [email protected] 3 points 4 months ago* (last edited 4 months ago) (1 children)

I wouldn't draw conclusions from random benchmarks like this without at least opening godbolt to see what's going on.

It really could be anything. e.g. final may have enabled inlining in more places, but this may have inlined a very uncommon branch in a hot loop, causing way more cache misses when fetching instructions. Writing compilers is hard, and all optimisation passes are using imperfect heuristics.

Compiling with PGO might make the results more compelling, if that wasn't already tried.

[–] [email protected] 1 points 4 months ago

As a side note, the final keyword is only tangentially related with inlining. It's killer feature is removing the need to do pointer dereferencing when calling virtual members of instances of classes that no longer require virtualization.

[–] [email protected] 2 points 4 months ago

I'd be curious to know what the difference in generated assembly was between the two. Would this affect things in a program without virtual classes?

[–] [email protected] 1 points 4 months ago

It does enable looking down classes duch that noone can accidentally inherit it. This could have benefit when writing non-performance critical Code.