We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Due to gcc 7 issue with lock free structures described in #1189 the following check fails
https://github.com/yugabyte/yugabyte-db/blob/master/src/yb/tablet/operations/operation_driver.cc#L93
Solution boost::atomic should be used instead of std::atomic
The text was updated successfully, but these errors were encountered:
#2545 [YBase] Use boost::amotic for op_id_copy_ member (128 bits stru…
d135ab8
…cture) Summary: Due to gcc 7 issue with lock free structures described in #1189 the following check fails https://github.com/yugabyte/yugabyte-db/blob/master/src/yb/tablet/operations/operation_driver.cc#L93 Solution: boost::atomic should be used instead of std::atomic Test Plan: Manual. Reinit db on centos build ``` ./yb_build.sh reinitdb ``` Reviewers: sergei Reviewed By: sergei Subscribers: ybase Differential Revision: https://phabricator.dev.yugabyte.com/D7362
d-uspenskiy
No branches or pull requests
Due to gcc 7 issue with lock free structures described in #1189 the following check fails
https://github.com/yugabyte/yugabyte-db/blob/master/src/yb/tablet/operations/operation_driver.cc#L93
Solution boost::atomic should be used instead of std::atomic
The text was updated successfully, but these errors were encountered: