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
Switched from boost::regex to std::regex #18720
Conversation
Doing a helgrind check uncovered a thread unsafe memory handling by boost::regex. Switching to std::regex solves that and reduces dependency on boost.
A new Pull Request was created by @Dr15Jones (Chris Jones) for master. It involves the following packages: HLTrigger/HLTcore @Martin-Grunewald, @silviodonato, @cmsbuild, @fwyzard, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
Running a helgrind job on reconstruction uncovered
From boosts documentation, boost::regex library is thread safe if |
@cmsbuild please test |
The tests are being triggered in jenkins. |
+1 |
This pull request is fully signed and it will be integrated in one of the next master IBs after it passes the integration tests. This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @smuzaffar |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1 |
Doing a helgrind check uncovered a thread unsafe memory handling
by boost::regex. Switching to std::regex solves that and reduces
dependency on boost.