diff options
| author | Jakub Jelinek <jakub@redhat.com> | 2025-01-08 23:12:02 +0100 |
|---|---|---|
| committer | Jakub Jelinek <jakub@gcc.gnu.org> | 2025-01-08 23:12:02 +0100 |
| commit | e5180fbcbcc356c71154413588288cbd30e5198d (patch) | |
| tree | 2d5cd6d75c41142a0eabbcfea3e0fc4f6308da18 /gcc/gimplify.cc | |
| parent | dcbd260a1dff3f93ed1aa6fd962e92bae8933dc6 (diff) | |
| download | gcc-e5180fbcbcc356c71154413588288cbd30e5198d.zip gcc-e5180fbcbcc356c71154413588288cbd30e5198d.tar.gz gcc-e5180fbcbcc356c71154413588288cbd30e5198d.tar.bz2 | |
c++: Honor complain in cp_build_function_call_vec for check_function_arguments warnings [PR117825]
The following testcase ICEs due to re-entering diagnostics.
When diagnosing -Wformat-security warning, we try to print instantiation
context, which calls tsubst with tf_none, but that in the end calls
cp_build_function_call_vec which calls check_function_arguments which
diagnoses another warning (again -Wformat-security).
The other check_function_arguments caller, build_over_call, doesn't call
that function if !(complain & tf_warning), so I think the best fix is
to do it the same in cp_build_function_call_vec as well.
2025-01-08 Jakub Jelinek <jakub@redhat.com>
PR c++/117825
* typeck.cc (cp_build_function_call_vec): Don't call
check_function_arguments if complain doesn't have tf_warning bit set.
* g++.dg/warn/pr117825.C: New test.
Diffstat (limited to 'gcc/gimplify.cc')
0 files changed, 0 insertions, 0 deletions