On Fri, Aug 8, 2014 at 2:43 PM, Dmitry Vyukov <dvyu...@google.com> wrote: >> Similar optimization could be used for tsan builtins, or some of the ubsan >> builtins (which is the reason why the pass is called sanopt). > > That would be great. > Note that tsan optimizations must be based around a different > criteria. Any unlock/release operations must reset set of already > checked locations.
Right, I think the general algorithm should be quite similar, only the KILL sets and actual check instructions would be different. Unfortunately I don't (yet) have any experience neither with TSan, nor with UBSan so I'd prefer to leave their optimization for future. The code should be straightforward to adapt (via templating or callbacking in couple of places). -Y
