I suppose that we could just add something in the general DESCRIPTION paragraph
like:
Besides the options listed below, sparse also accepts many C compiler command
line options.
but that's not very helpful (at least to me). For my use, I made a short text
file of other (not documented in sparse.1) command line options. Should these
be added to sparse.1 or elsewhere or not at all? (Of course, some of these
could be incorrect. :)
thanks,
--
~Randy
==========
sparse additional command-line options
(as of 2018.0123)
-ansi set C89 standard
-Dsymbol[=value] define a symbol plus an optional value for it
-dD dump macro definitions
-E preprocess only
-G[ ][0] ignored
-I -I- == #split_include
-Ipath #add_include "path/"
-I path
-include filename
-imacros filename
-isystem filename #add_isystem "path/"
-idirafter path #add_dirafter "path/"
-MF arg ignored
-MQ arg ignored
-MT arg ignored
-m64 set ARCH_LP64
-m32 set ARCH_LP32
-msize-llp64 set ARCH_LLP64
-msize-long set msize_long
-mbig-endian set big_endian
-mlittle-endian clear big_endian
-nostdinc #nostdinc
-o[ ]filename output filename; ignored
-O{0..9,s} set optimize level
-std=standard c89 or iso9899:1990 == C89
iso9899:199409 == C94
c99 or c9x or iso9899:1999 or iso9899:199x == C99
gnu89 == GNU89
gnu99 or gnu9X == GNU99
c11 or c1x or iso9899:2011 == C11
gnu11 == GNU11
-U symbol #undef symbol
-v[ ]entry debug entry
-v[ ]dead debug dead
-v[v...] increment verbose level
--param[= ][value] ignored
--version print sparse version
#####
--
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
