aboutsummaryrefslogtreecommitdiff
path: root/clang/lib/Frontend/CompilerInvocation.cpp
diff options
context:
space:
mode:
authorGeorgii Rymar <grimar@accesssoftek.com>2020-11-27 11:57:03 +0300
committerGeorgii Rymar <grimar@accesssoftek.com>2020-12-01 11:09:30 +0300
commit87481068fddf29e913b129b9c962ba761ae478c8 (patch)
treeb879df1db0f30e6553e13780cc3afeff668fdfff /clang/lib/Frontend/CompilerInvocation.cpp
parent2e5aaf65a344ae804343bfed6326ef33f61586b0 (diff)
downloadllvm-87481068fddf29e913b129b9c962ba761ae478c8.zip
llvm-87481068fddf29e913b129b9c962ba761ae478c8.tar.gz
llvm-87481068fddf29e913b129b9c962ba761ae478c8.tar.bz2
[llvm-readelf] - Switch to using from `reportWarning` to `reportUniqueWarning` in `DynRegionInfo`.
This is a part of the plan we had previously to convert all calls to `reportUniqueWarning` and then rename it to just `reportWarning`. I was a bit unsure about this particular change at first, because it doesn't add a new functionality: seems it is impossible to trigger a warning duplication currently. At the same time I find the idea of the plan mentioned very reasonable. And with that we will be sure that `DynRegionInfo` can't report duplicate warnings, what looks like a nice feature for possible refactorings and further tool development. Differential revision: https://reviews.llvm.org/D92224
Diffstat (limited to 'clang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions