On Feb 12, 2009, at 11:37 PM, Daniel Dunbar wrote:
> My intent was that clang's own tests would always use the clang
> compiler binary, not the driver. The idea is that the driver is the
> end-user tool, and as such should go as fast as possible. On the other
> hand, for development and testing we get the alloc/free behavior so we
> shake out bugs like you mentioned.
Sure, but the real testing---the testing that we care about most---
occurs when we use the driver. Say, when I take the clang that's in my
path (always a debug version) and try to build some big application
with it. Usually, ownership bugs are going to occur in larger
translation units, which will occur within applications but not
necessarily within our test-suite.
Besides, aren't we eventually going to merge the compiler binary and
the driver into one executable?
>
> Does this seem reasonable, or are you still sad? :)
*sniff*
- Doug
_______________________________________________
cfe-commits mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
