[llvm-bugs] [Bug 36767] New: Some warnings do not have -Wno- options (for example -Wno-disabled-macro-expansion -Wno-global-constructors)

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=36767

            Bug ID: 36767
           Summary: Some warnings do not have -Wno- options (for example
                    -Wno-disabled-macro-expansion
                    -Wno-global-constructors)
           Product: clang
           Version: 6.0
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: C++
          Assignee: unassignedclangbugs at nondot.org
          Reporter: pbristow at hetp.u-net.com
                CC: dgregor at apple.com, llvm-bugs at lists.llvm.org

Some warnings do not seem to have -Wno- options

(for example  -Wno-disabled-macro-expansion -Wno-global-constructors).

During development of Boost libraries, authors are encouraged to improve the
code to avoid warnings 

https://svn.boost.org/trac10/wiki/Guidelines/WarningsGuidelines

Sadly this has often proved impossible for all platforms/compilers.

It has been found useful to be able to enable more/all warnings and then
selectively silence individual warnings to try to obtain a warnings-free
compilation.  This allows the many Boost users to get a clean compilation free
from clutter from warnings.  (A recent compilation of Boost.Test produced 247
warnings!)

The act of supressing a warning documents that the warning has been considered
and is not judged significant.

To make this possible (and to make things simple for the user to be able to
assume that all warnings can be quieted rather than try, but fail, for some)
*all* -W should have a corresponding -Wno- command (even if -Wextra ... has
enabled them).

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20180316/a7165aa2/attachment.html>