-
Notifications
You must be signed in to change notification settings - Fork 300
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
Use shared linkage for benchmarks #1336
Conversation
@mikea Any concerns about shared linkage affecting benchmark performance? If it would make benchmarking less accurate we could disable it in the benchmark/profile configurations. |
I just noticed nodejs download failureus in the tests, looks like a bad rebase on my side. Fix coming. |
|
2b1dbc3
to
c6de41d
Compare
Thank you! Merged it so this can be unblocked. |
Looks like this doesn't work on Windows 🫤 |
We already use shared linkage for tests – cc_test uses shared linkage by default. This allows us to compile benchmark binaries for CI debug/ASAN builds, which would otherwise be prohibitively large. For now, this is only enabled on Linux.
c6de41d
to
4394f96
Compare
Investigated what it would take to support shared linkage on Windows – apparently global variables that should be visible across libraries need to be specifically annotated as |
We already use shared linkage for tests –
cc_test
uses shared linkage by default. This allows us to compile benchmark binaries for CI debug/ASAN builds, which would otherwise be prohibitively large.