diff options
| author | Jakub Jelinek <jakub@redhat.com> | 2020-03-26 10:35:52 +0100 |
|---|---|---|
| committer | Jakub Jelinek <jakub@redhat.com> | 2020-03-26 10:35:52 +0100 |
| commit | da920d0c46c38fe25ee0b597a8698d3a4d098f3c (patch) | |
| tree | bd1bd9d225cc9a416eb2df6b4c01883d97207e63 /gcc/tree-ssa-propagate.c | |
| parent | d6730f06420106af01e26414f046626b5292565d (diff) | |
| download | gcc-da920d0c46c38fe25ee0b597a8698d3a4d098f3c.zip gcc-da920d0c46c38fe25ee0b597a8698d3a4d098f3c.tar.gz gcc-da920d0c46c38fe25ee0b597a8698d3a4d098f3c.tar.bz2 | |
tree: Fix -fcompare-debug issues due to protected_set_expr_location [PR94323]
The following testcase FAILs since recently when the C++ FE started calling
protected_set_expr_location more often.
With -g, it is called on a STATEMENT_LIST that contains a DEBUG_BEGIN_STMT
and CLEANUP_POINT_EXPR, and as STATEMENT_LISTs have !CAN_HAVE_LOCATION_P,
nothing is set. Without -g, it is called instead on the CLEANUP_POINT_EXPR
directly and changes its location.
The following patch recurses on the single non-DEBUG_BEGIN_STMT statement
of a STATEMENT_LIST if any to make the two behave the same.
2020-03-26 Jakub Jelinek <jakub@redhat.com>
PR debug/94323
* tree.c (protected_set_expr_location): Recurse on STATEMENT_LIST
that contains exactly one non-DEBUG_BEGIN_STMT statement.
* g++.dg/debug/pr94323.C: New test.
Diffstat (limited to 'gcc/tree-ssa-propagate.c')
0 files changed, 0 insertions, 0 deletions