Thread (12 messages) 12 messages, 6 authors, 2015-11-24

Re: [PATCH] video: constify geode ops structures

From: Joe Perches <joe@perches.com>
Date: 2015-11-10 22:17:19
Also in: kernel-janitors, lkml

On Wed, 2015-11-11 at 01:02 +0300, Dan Carpenter wrote:
On Tue, Nov 10, 2015 at 12:49:29PM -0800, Joe Perches wrote:
quoted
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?
I'm not sure I understand the question.  What would the warning say?
Perhaps something like:

declaration of struct <foo> converted to const by __attribute__((do_const))
We'll hopefully automatically make over 3000 structs const.  I
understand warning that people should make structs const when possible
but I don't understand why we would want to remove auto consting?
I'm not suggesting removing the attribute.
It seems sensible enough.

I just think the plug-in should at least optionally
note the instances when non-const declarations are
converted to const.
Putting __do_const in the .h file is basically the same as marking
every struct of that type as const in the .c file.
Not for a reader of the code that doesn't first
inspect the header files.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help