https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71445
Carlos O'Donell <carlos at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |carlos at redhat dot com
--- Comment #13 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Adhemerval Zanella from comment #12)
> After checking the work required for enable symbol versioning wrapper on
> libsanitizer I am more inclined to go with always ignore the high bits (at
> least for backports). The versioning enablement will require some changes
> and I foresee it will generate some discussion in sanitizer side before a
> settle solution is used. Any suggestions?
+1
That sounds like the most sensible course of action.
The real solution IMO is for the interposer to provide all the various versions
of a function and sanitize them each as needs be. There is no other way around
this and this was a problem that was going to happen some day, we are just
having it happen today because of the changes in glibc.
