[cfe-commits] adding '-fasan' flag

[Chris Lattner]

On Nov 16, 2011, at 2:59 PM, Kostya Serebryany wrote:
> I think, more generally, we should have a naming strategy for options
> controlling runtime checks. For the IOC checks, it would be useful to have
> fine-grained control
> FYI
> For AddressSanitizer we may also need fine-grained control in the future. 
> -faddress-sanitizer-[no-]reads
> -faddress-sanitizer-[no-]stack
> -faddress-sanitizer-[no-]globals

Kostya and I discussed this offline, but I'd really really like to keep the number of public knobs to a minimum.  The long term direction I'd like to see clang go is to have a small number of runtime checks (asan, ioc, array checks, whatever) and then have -fcatch-undefined-behavior turn on some reasonable set of them.  Having a small number of knobs to tweak each of these runtime checkers is fine, but they should be a *small* number and easily explainable.

Flags with unitless magic numbers attached to them (like the gcc unroll thresholds) are highly frowned upon :)

-Chris

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20111116/4d390bfd/attachment.html>