https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118204
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> --- (In reply to Sam James from comment #1) > Note that for > https://gcc.gnu.org/onlinedocs/gcc/Instrumentation-Options.html#index- > fsanitize-trap, we already document the incompatibility with vptr: > > Currently this feature works with -fsanitize=undefined (and its suboptions > > except for -fsanitize=vptr), [...] > > If -fsanitize-trap=undefined or -fsanitize-trap=all is used and > > -fsanitize=vptr is enabled on the command line, the instrumentation is > > silently ignored as the instrumentation always needs libubsan support, > > -fsanitize-trap=vptr is not allowed. Though I have to admit, the wording here is hard to understand. Does it mean the instrumentation for vptr is not done if -fsanitizer=undefined is used? I understand the last part though; even though it should be a separate sentence or using a semicolon instead of a comma.
