-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Emit vtables once #521
Emit vtables once #521
Conversation
Codecov Report
@@ Coverage Diff @@
## master #521 +/- ##
=======================================
Coverage 99.69% 99.69%
=======================================
Files 54 54
Lines 17322 17325 +3
=======================================
+ Hits 17270 17273 +3
Misses 52 52 |
Does this potentially have any effect on benchmarks? |
Unlikely, as we don't call exception destructors (some runtime library does so it cannot inline them anyway). |
b7adc8e
to
7f53d7d
Compare
This fixes -Wweak-vtable warnings
7f53d7d
to
5d38cab
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would be nice to see some numbers, I hope there are no weird regressions.
|
The size of |
This fixes -Wweak-vtable warnings, helpful for #508.
The effect in fizzy library is the following: vtables and typeinfos (V) are generates once in the
exceptions.cpp.o
instead of all files they were used. And the destructors are notinline
any more (W -> T). This is good change as they are always cold.I'm not convinced the impact is worth the trouble.