[cfe-commits] r169144 - in /cfe/trunk: include/clang/Driver/Options.td include/clang/Frontend/CodeGenOptions.h lib/CodeGen/BackendUtil.cpp lib/Driver/SanitizerArgs.h lib/Driver/Tools.cpp lib/Frontend/CompilerInvocation.cpp test/Driver/fsanitize-blacklist.c

[Sean Silva]

Ping. Any progress on this?

-- Sean Silva


On Fri, Jul 19, 2013 at 1:05 PM, Sean Silva <silvas at purdue.edu> wrote:

>
>
>
> On Fri, Jul 19, 2013 at 5:41 AM, Alexey Samsonov <samsonov at google.com>wrote:
>
>> Hi Sean!
>>
>> Sorry for the late reply...
>>
>> What is the best place for describing the file format? The general format
>> is shared among all sanitizer tools, but there can be sanitizer-specific
>> entries as well.
>> E.g. we can describe -fsanitize-blacklist/-fno-sanitize-blacklist flags
>> in UsersManual and give a link to new SanitizerSpecialCaseList.rst file,
>> that would describe the format and common
>> functionality. Then, in each of the AddressSanitizer, ThreadSanitizer and
>> MemorySanitizer pages we may also give a link to SanitizerSpecialCaseList
>> and describe tool-specific additions (if any).
>> Does it make sense?
>>
>>
> Splitting out the description of the format makes sense to me.
>
> Is there a particular reason you suggested the name
> SanitizerSpecialCaseList.rst instead of SanitizerBlacklist.rst (for
> consistency with the commandline option name)?
>
> -- Sean Silva
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20130801/d0a9824b/attachment.html>