Re: [creduce-dev] Avoiding syntax warnings and errors

2018-03-15 Thread Yang Chen
Hi Moritz, Thanks for the prompt patch! On 2018-03-15 02:52, Moritz Pflanzer wrote: Hi John, On 14 Mar 2018, at 14:53, John Regehr wrote: Regarding try-catch, yes, we'd like to have a pass for that. I added a note about this to our TODO list, but mostly we're too busy for adding new stuff

Re: [creduce-dev] Avoiding syntax warnings and errors

2018-03-15 Thread Moritz Pflanzer
Hi John, > On 14 Mar 2018, at 14:53, John Regehr wrote: > > Regarding try-catch, yes, we'd like to have a pass for that. I added a note > about this to our TODO list, but mostly we're too busy for adding new stuff > these days. I quickly created a simple clang_delta pass to remove/simplify tr

Re: [creduce-dev] Avoiding syntax warnings and errors

2018-03-14 Thread John Regehr
Hi Vegard, I'll agree with Yang that the point of C-Reduce is basically to *not* worry about any of the things you mention, deferring those problems to the interestingness test. I typically include some tests for warnings in the interestingness test, or else just manually fix up the warnings a

Re: [creduce-dev] Avoiding syntax warnings and errors

2018-03-13 Thread Yang Chen
Hi Vegard, On 03/13/2018 12:08 PM, Vegard Nossum wrote: Hi, First of all, thanks for C-reduce! It's extremely useful and valuable. I am trying to run C-reduce on a large number of (large-ish, preprocessed) source files and I have run into the following problems and/or minor annoyances: Espec