Hi, On Wed, May 31, 2017 at 2:45 PM, David Rientjes <rientjes@xxxxxxxxxx> wrote: > On Wed, 31 May 2017, Doug Anderson wrote: > >> > Again, I defer to maintainers like Andrew and Ingo who have to deal with >> > an enormous amount of patches on how they would like to handle it; I don't >> > think myself or anybody else who doesn't deal with a large number of >> > patches should be mandating how it's handled. >> > >> > For reference, the patchset that this patch originated from added 8 lines >> > and removed 1, so I disagree that this cleans anything up; in reality, it >> > obfuscates the code and makes the #ifdef nesting more complex. >> >> As Matthias said, let's not argue about ifdeffs and instead talk about >> adding "maybe unused". 100% of these cases _can_ be solved by adding >> "maybe unused". Then, if a maintainer thinks that an ifdef is cleaner >> / better in a particular case, we can use an ifdef in that case. >> >> Do you believe that adding "maybe unused" tags significantly uglifies >> the code? I personally find them documenting. >> > > But then you've eliminated the possibility of finding dead code again, > which is the only point to the warning :) So now we have patches going to > swamped maintainers to add #ifdef's, more LOC, and now patches to sprinkle > __maybe_unused throughout the code to not increase LOC in select areas but > then we can't find dead code again. True, once code is marked __maybe_unused once then it can no longer be found later, even if it becomes completely dead. ...but this is also no different for __maybe_unused code that is _not_ marked as "static inline". Basically, my argument here is that "static inline" functions in ".c" files should not be treated differently than "static" functions in ".c" files. We have always agreed to add __maybe_unused for "static" functions. Also: allowing us to leave the warning turned on (and have no false positives reported) mean that, as new code is added we'll be able to find problems in the new code. This is where it's most important. > My suggestion is to match gcc behavior and if anybody is in the business > of cleaning up truly dead code, send patches. Tools exist to do this > outside of relying on a minority compiler during compilation. Otherwise, > this is simply adding more burden to already swamped maintainers to > annotate every single static inline function that clang complains about. > I'd prefer to let them decide and this will be the extent of my > participation in this thread. Maybe Matthias can give actual stats here, but I think "every single" overstates the issue a bit. I get the impression we're talking something like ~30-40 patches that don't actually delete dead code and just add "maybe unused". Given that nobody has ever looked for these functions before, I'd expect that new code is unlikely to cause a new deluge of patches. Note also that Matthias started a bigger thread to discuss this (subject: [RFC] clang: 'unused-function' warning on static inline functions). Maybe we should move the discussion there so it's not so scattered? -Doug -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>
