diff options
author | Fangrui Song <maskray@google.com> | 2020-04-22 09:53:35 -0700 |
---|---|---|
committer | Fangrui Song <maskray@google.com> | 2020-04-23 18:26:06 -0700 |
commit | 14aaf4457c641bd5130072ba2a035e254b92fad3 (patch) | |
tree | 24bc472829a897f452e018eef29183c1b18f7bce /llvm/lib/Bitcode/Writer/BitcodeWriter.cpp | |
parent | 2f9d1533d94699d943b34f1ba87f80fbd2e8c144 (diff) | |
download | llvm-14aaf4457c641bd5130072ba2a035e254b92fad3.zip llvm-14aaf4457c641bd5130072ba2a035e254b92fad3.tar.gz llvm-14aaf4457c641bd5130072ba2a035e254b92fad3.tar.bz2 |
[Sema] Split off warn_impcast_integer_float_precision_constant into -Wimplicit-const-int-float-conversion
Currently, both `warn_impcast_integer_float_precision_constant` and
`warn_impcast_integer_float_precision` are covered by
-Wimplicit-int-float-conversion, but only the ..._constant warning is on
by default.
`warn_impcast_integer_float_precision_constant` likely flags real problems
while `warn_impcast_integer_float_precision` may flag legitimate use
cases (for example, `int` used with limited range supported by `float`).
If -Wno-implicit-int-float-conversion is used, currently there is no way
to restore the ..._constant warning. This patch adds
-Wimplicit-const-int-float-conversion to address the issue. (Similar to
the reasoning in https://reviews.llvm.org/D64666#1598194)
Adapted from a patch by Brooks Moses.
Reviewed By: nickdesaulniers
Differential Revision: https://reviews.llvm.org/D78661
Diffstat (limited to 'llvm/lib/Bitcode/Writer/BitcodeWriter.cpp')
0 files changed, 0 insertions, 0 deletions