cleanup mutex and signalling in ExecuteWrapper
found this while examining issues reported by clang-tidy. Judging from the code, the original intention was to somehow lock access to the mbSignal field in ExecuteWrapper, but since we were not locking when writing to that field, and that field was not volatile, it surprises me that this worked very well at all. We can accomplish the same end more reliably by just marking the field as volatile and not doing any locking at all. Change-Id: I388c7082a809b6aca5a3c8981625f55cfef3cfcd Reviewed-on: https://gerrit.libreoffice.org/60184 Tested-by: Jenkins Reviewed-by:Noel Grandin <noel.grandin@collabora.co.uk>
Showing
Please
register
or
sign in
to comment