https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78267
--- Comment #48 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot
Uni-Bielefeld.DE> ---
> --- Comment #47 from Maxim Ostapenko <m.ostapenko at samsung dot com> ---
[...]
> Rainer, sorry for a dumb question: are you going to commit your fix for
> darwin_availabilityinternal part? Or should I just apply a patch from comment
> #15?
> I've completely messed in this discussion thus I don't understand clearly what
> should I do now.
Not a dumb question at all: I'm somewhat lost in this PR myself. I
guess we need to make a concerted effort to test the combo of the
darwin_availabilityinternal fix and the __BLOCKS__ guard in
sanitizer_mac.cc on at last Darwin 16, 15 and 14. I can do 16 myself,
but probably not before Friday.
Rainer
