On Thu, Nov 29, 2012 at 10:04 AM, Richard Smith <[email protected]>wrote:
> On Wed, Nov 28, 2012 at 9:50 PM, Anna Zaks <[email protected]> wrote: > >> >> On Nov 27, 2012, at 2:16 PM, Alexey Samsonov wrote: >> >> > Hi kcc, rsmith, >> > >> > This patch expose to users three more sanitizers: >> > 1) init-order sanitizer: initialization-order checker. >> > Status: usable, but may produce false positives w/o proper >> blacklisting. >> > 2) use-after-return sanitizer >> > Status: implemented, but heavily understed. Should be optional, as >> > it significanlty slows program down. >> > 3) use-after-scope sanitizer >> > Status: in progress, also see phabricator patches D140 and D141. >> > What do you think on general approach for exposing non-default ASan >> > features, and of branding? >> > >> >> It might be useful to document these options somewhere as well as the >> state of usability / supported OSs / false positive rates / overhead for >> each one. The info above will change and is valuable to whoever would want >> to experiment with these. >> > > Thanks, good point, this patch should also update docs/UsersManual.html, > which documents the available -fsanitize= values. > None of these options are as usable as the main asan yet. So, if we document them, we need to mark them as "experimental". --kcc
_______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
