On Tue, Jul 18, 2017 at 7:46 PM, Pavel Roskin <plroskin@xxxxxxxxx> wrote: > Yes, that works! I wish I thought of it earlier and did not waste time > writing that patch. > > That option may still be useful if sparse attempts to imitate the > behavior of specific gcc versions (in addition to the defines). I will skip the patch for now. Yes it is more convenient to give one command line options and it set 3 macros. I am not sure the complexity justify it. When you specify the gcc version, there is also implicit version specific behavior go with it. I can see user file bugs said I give sparse gcc version X, but gcc has macro Y in X. That is not the case with sparse, that is a bug. I don't want to give the user false impression that sparse can set a gcc version and simulate the gcc version specific behavior. It is simpler just put the version specific macro into a header file and ask sparse to include it. You should be able to add that to command line as well. Chris -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
