-
Notifications
You must be signed in to change notification settings - Fork 15
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
Backport of tbb cleanup #291
Backport of tbb cleanup #291
Conversation
…ous other warnings found by clang-10
Benchmarks are here. These were run on lnx7188, so the CPU benchmarks may differ some, and the multiple events in flight show a known intermittent anomaly on the first point. Physics should be identical (and do appear to be) to the #240 validation plots. |
considering the amount of changes, I think that this will become v2.1.0 release once merged, instead of v2.1.0-2 patch. |
I guess it either requires a PR for CMSSW or this backport should be made more targeted to be compatible with the CMSSW release. |
I suspect that is not sufficient because of } else if (build == "fullVector") {
isFV = true;
buildFunction_ = mkfit::runBuildingTestPlexFV; in https://github.com/cms-sw/cmssw/blob/eb134e644ee5255fc0656f1e4181bfca7203306e/RecoTracker/MkFit/plugins/MkFitProducer.cc#L63-L65 Line 15 in 27f790c
but could missing the definition lead to link failure? |
Yes, it does lead to a link failure. (I've now done the test build with CMSSW that I should have before making the PR.) |
I've verified that the CMSSW MkFit plugin compiles and links with the latest two commits, apologies for not testing that before making the PR. I could make the backport more targeted, but it will take more time. (That we're still declaring |
Just to say it out loud, I'm thinking to remove the use of FullVector from CMSSW side quickly after the mkFit external gets updated (and update https://github.com/trackreco/cmssw as well). |
This PR backports the TBB cleanup to the v2.0.1_patches branch in order to address issue #290 updating TBB. The simplest way to do the backport was to merge most of the CUDA removal PR #283 and all of the FullVector removal PR #286 so besides the TBB update it also removes a lot of dead code.
There shouldn't be an change in physics or computing performance, but I'll try running validation at Cornell (the input file for this older version is no longer in place on phi3).