[cfe-commits] [PATCH] [ubsan] Add support for -fsanitize-blacklist

[Alexey Samsonov]

I think that making blacklist available in Clang is a good idea.
I agree with Richard's comment as well.


On Thu, Jan 17, 2013 at 12:50 AM, Richard Smith <richard at metafoo.co.uk>wrote:

> On the clang side, it seems messy and error-prone to distribute the
> checking for blacklisting across all the callers of EmitCheck, but I
> understand that you're trying to avoid generating the check condition
> for blacklisted functions. Maybe we could make a separate struct
> containing just the Sanitize* flags, and in the CodeGenFunction
> constructor bind a reference to either the global set of flags or a
> set of all-false flags, depending on whether we're blacklisted? This
> would also make it easier to blacklist specific sanitizers in specific
> functions later.
>
> On Wed, Jan 16, 2013 at 12:08 PM, Will Dietz <wdietz2 at illinois.edu> wrote:
> > Minor touchup to clang patch, thanks!
> >
> > ~Will
> >
> > On Wed, Jan 16, 2013 at 11:37 AM, Will Dietz <wdietz2 at illinois.edu>
> wrote:
> >> Attached are two patches.
> >>
> >> First applies to clang and uses the blacklist to avoid instrumenting
> >> the source files or functions specified.  Lit test included.
> >>
> >> The other is a small change to llvm to make the "Blacklist" class
> >> visible to Clang.  Not sure I understand the header organization
> >> system well enough, let me know if it belongs elsewhere.
> >>
> >> Thanks!
> >>
> >> ~Will
> >
> > _______________________________________________
> > cfe-commits mailing list
> > cfe-commits at cs.uiuc.edu
> > http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
> >
> _______________________________________________
> cfe-commits mailing list
> cfe-commits at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
>



-- 
Alexey Samsonov, MSK
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20130117/eb052577/attachment.html>