diff options
author | Haojian Wu <hokein.wu@gmail.com> | 2024-08-22 10:35:49 +0200 |
---|---|---|
committer | GitHub <noreply@github.com> | 2024-08-22 10:35:49 +0200 |
commit | c368a720a0b40bb8fe4aff3971fe9a7009c85aa6 (patch) | |
tree | 19a702824eaa01c410c8e831740dfedbbc850c48 /lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.h | |
parent | fab515ca7f3c64b47dd94a92156a4696771ee22a (diff) | |
download | llvm-c368a720a0b40bb8fe4aff3971fe9a7009c85aa6.zip llvm-c368a720a0b40bb8fe4aff3971fe9a7009c85aa6.tar.gz llvm-c368a720a0b40bb8fe4aff3971fe9a7009c85aa6.tar.bz2 |
[clang] Merge lifetimebound and GSL code paths for lifetime analysis (#104906)
In the current lifetime analysis, we have two parallel code paths: one
for lifetimebound and another for GSL. These paths perform the same
logic, both determining whether to continue visiting subexpressions.
This PR merges the two paths into a single code path. As a result, we'll
reduce the overhead by eliminating a redundant visit to subexpressions.
The change is mostly NFC (No Functional Change). The only notable
difference is that when a subexpression is visited due to either
lifetimebound or GSL, we will prioritize the lifetimebound path. This
means the final diagnostic will be -Wdangling (rather than both
`-Wdangling` and `-Wdangling-gsl`)
This might cause a slight change in behavior if the -Wdangling
diagnostic is disabled, but I think this is not a major concern since
both diagnostics are enabled by default.
Fixes #93386
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.h')
0 files changed, 0 insertions, 0 deletions