On Sat, 24 Nov 2018 14:29:59 +0100 Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx> wrote: > cgcc and sparse didn't knew about these option but they may > be needed for any project that uses cgcc as a wrapper around > gcc + sparse. > Apart from some minor typos in commit messages the changes look really great. I also tested the changes and found no issues. Thank you Luc, it's appreciated. For the whole series: Reviewed-by: Antonio Ospite <ao2@xxxxxx> Ciao, Antonio > Changes from the separated patches: > * '-o <file>' and '-x <language>' are now forwarded from cgcc > to the checker and the compiler. > * cgcc now ignores -o's argument to not treat it as another > option or input filename. > * cgcc and sparse now ignore -x's argument to not treat it as > another option or input filename. > * sparse ignore '-o -' (since stdout is its default). > * sparse as a checker ignore the -o redirection of stdout > but not if expected to produce an output, for example > when -E or -dD is used. > > Luc Van Oostenryck (5): > teach sparse about '-o <file>' > teach sparse about '-x <language>' > cgcc: add support to ignore argument(s) of options > cgcc: teach about '-o <file>' > cgcc: teach about '-x c' > > cgcc | 27 +++++++++++++++++++++++++-- > lib.c | 21 +++++++++++++++++++++ > lib.h | 1 + > sparse.c | 3 +++ > 4 files changed, 50 insertions(+), 2 deletions(-) > > -- > 2.19.0 > -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
