[cfe-commits] [PATCH] expected-no-diagnostics for -verify (was: Re: r164677 - )
andyg1001 at hotmail.co.uk
Wed Oct 10 01:21:25 PDT 2012
** bump ** :o)
I've had to resync and attach the patch again here; a test-case needed to be
updated to reflect changes in trunk. The patch now is taken against
On Saturday, October 06, 2012 10:59 PM, Andy Gibbs wrote:
> Was there any interest in this patch? Please let me know if there are any
> changes that should be made, or whether it is good to be committed? (or
> even whether I was barking up the wrong tree...?!)
> (If any were unable to receive the patch -- I know that sometimes Apple
> users have problems with my attachments! -- then it can be viewed directly
> at [...snip...])
> On Tuesday, October 02, 2012 5:32 PM, Andy Gibbs wrote:
>> Attached is a patch that adds an 'expected-no-diagnostics' directive
>> to -verify. This can then be used, as discussed, to flag files that are
>> expected to produce any diagnostics at all. -verify has then been
>> to generate an error if no expected-* directives are found (for example,
>> the RUN line doesn't specify the source file!). I've also made it so
>> the user cannot put 'expected-no-diagnostics' in with other expected-*
>> directives (to avoid mistakes!).
>> The complete patch is rather large, but I've grouped the changes to
>> VerifyDiagnosticConsumer to the top of the file along with the additional
>> test-case. The rest of the patch makes the necessary changes to fix 580
>> test-cases which now (in almost all cases) need to have the
>> 'expected-no-diagnostics' directive.
>> Comments / questions welcome!
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 277806 bytes
Desc: not available
More information about the cfe-commits