diff options
| author | Jakub Jelinek <jakub@redhat.com> | 2024-04-12 20:53:10 +0200 |
|---|---|---|
| committer | Jakub Jelinek <jakub@redhat.com> | 2024-04-12 20:54:59 +0200 |
| commit | 91146346f57cc54dfeb2669347edd0eb3d13af7f (patch) | |
| tree | 4b9fabf7b6b37971cabb792a3780dd794bde89d2 /gcc/cp | |
| parent | d74fe10b13336b9de2e025ced4af00a25ff1d3e7 (diff) | |
| download | gcc-91146346f57cc54dfeb2669347edd0eb3d13af7f.zip gcc-91146346f57cc54dfeb2669347edd0eb3d13af7f.tar.gz gcc-91146346f57cc54dfeb2669347edd0eb3d13af7f.tar.bz2 | |
c++: Fix bogus warnings about ignored annotations [PR114691]
The middle-end warns about the ANNOTATE_EXPR added for while/for loops
if they declare a var inside of the loop condition.
This is because the assumption is that ANNOTATE_EXPR argument is used
immediately in a COND_EXPR (later GIMPLE_COND), but simplify_loop_decl_cond
wraps the ANNOTATE_EXPR inside of a TRUTH_NOT_EXPR, so it no longer
holds.
The following patch fixes that by adding the TRUTH_NOT_EXPR inside of the
ANNOTATE_EXPR argument if any.
2024-04-12 Jakub Jelinek <jakub@redhat.com>
PR c++/114691
* semantics.cc (simplify_loop_decl_cond): Use cp_build_unary_op with
TRUTH_NOT_EXPR on ANNOTATE_EXPR argument (if any) rather than
ANNOTATE_EXPR itself.
* g++.dg/ext/pr114691.C: New test.
Diffstat (limited to 'gcc/cp')
| -rw-r--r-- | gcc/cp/semantics.cc | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/gcc/cp/semantics.cc b/gcc/cp/semantics.cc index abaa4a3..02c7c1b 100644 --- a/gcc/cp/semantics.cc +++ b/gcc/cp/semantics.cc @@ -799,7 +799,11 @@ simplify_loop_decl_cond (tree *cond_p, tree body) *cond_p = boolean_true_node; if_stmt = begin_if_stmt (); - cond = cp_build_unary_op (TRUTH_NOT_EXPR, cond, false, tf_warning_or_error); + cond_p = &cond; + while (TREE_CODE (*cond_p) == ANNOTATE_EXPR) + cond_p = &TREE_OPERAND (*cond_p, 0); + *cond_p = cp_build_unary_op (TRUTH_NOT_EXPR, *cond_p, false, + tf_warning_or_error); finish_if_stmt_cond (cond, if_stmt); finish_break_stmt (); finish_then_clause (if_stmt); |