On Tue, 2015-11-10 at 12:34 -0800, Kees Cook wrote:
We can't make everything work just by static
analyzers and checkpatch.pl runs (meaning the "backstop" comment
above).
Additionally, having the plugin infrastructure gets us the ability to
do things that aren't presently possible (see the thread on the
initify plugin, which can't be done in source alone).
#define __do_const __attribute__((do_const))
...
#ifndef __do_const
#define __do_const
#endif
I think it's always better for the reader to know that a
const struct declaration is used over a non-const struct
when the compiler, via plug-in extension, could convert
the declaration to const.
Is there a warning/info message produced by gcc and the
plug-in when a non-const declaration is converted to
const because of this attribute?